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

["Dongjoon Hyun (Jira)" <ji...@apache.org>]

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

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

Issue resolved by pull request 38231
[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
>            Assignee: Zhongwei Zhu
>            Priority: Minor
>             Fix For: 3.4.0
>
>
> 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