You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@spark.apache.org by "Dongjoon Hyun (Jira)" <ji...@apache.org> on 2022/12/10 23:22:00 UTC

[jira] [Resolved] (SPARK-41460) Introduce IsolatedThreadSafeRpcEndpoint to extend IsolatedRpcEndpoint

     [ https://issues.apache.org/jira/browse/SPARK-41460?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dongjoon Hyun resolved SPARK-41460.
-----------------------------------
    Fix Version/s: 3.4.0
       Resolution: Fixed

Issue resolved by pull request 38995
[https://github.com/apache/spark/pull/38995]

> Introduce IsolatedThreadSafeRpcEndpoint to extend IsolatedRpcEndpoint 
> ----------------------------------------------------------------------
>
>                 Key: SPARK-41460
>                 URL: https://issues.apache.org/jira/browse/SPARK-41460
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 2.4.8, 3.0.3, 3.1.3, 3.2.2, 3.3.1
>            Reporter: wuyi
>            Assignee: wuyi
>            Priority: Major
>             Fix For: 3.4.0
>
>
> 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.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org