Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
2.4.8, 3.0.3, 3.1.3, 3.2.2, 3.3.1
-
None
Description
The current RpcEndpoint extension to IsolatedRpcEndpoint always implies that it's thread-safe. However, it's not explicit to developers. So people may mistakenly override the IsolatedRpcEndpoint#threadCount with more than 1 threadCount leading to the thread-safety broken.
Attachments
Issue Links
- relates to
-
SPARK-29398 Allow RPC endpoints to use dedicated thread pools
- Resolved
- links to