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

Posted to issues@spark.apache.org by "Apache Spark (Jira)" <ji...@apache.org> on 2022/10/13 04:04:00 UTC

[jira] [Commented] (SPARK-40778) Make HeartbeatReceiver as an IsolatedRpcEndpoint

    [ https://issues.apache.org/jira/browse/SPARK-40778?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17616766#comment-17616766 ] 

Apache Spark commented on SPARK-40778:
--------------------------------------

User 'warrenzhu25' has created a pull request for this issue:
https://github.com/apache/spark/pull/38231

> Make HeartbeatReceiver as an IsolatedRpcEndpoint
> ------------------------------------------------
>
>                 Key: SPARK-40778
>                 URL: https://issues.apache.org/jira/browse/SPARK-40778
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>    Affects Versions: 3.3.0
>            Reporter: Zhongwei Zhu
>            Priority: Minor
>
> All RpcEndpoint including HeartbeatReceiver in driver are sharing one thread pool. When there're lots of rpc messages queued, the waiting process time of heartbeat time could easily exceed heartbeat timeout. Make HeartbeatReceiver extends IsolatedRcpEndpoint then it has dedicated single thread to process heartbeat



--
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