You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Wenchen Fan (Jira)" <ji...@apache.org> on 2019/11/12 08:26:00 UTC
[jira] [Assigned] (SPARK-29298) Separate block manager heartbeat
endpoint from driver endpoint
[ https://issues.apache.org/jira/browse/SPARK-29298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan reassigned SPARK-29298:
-----------------------------------
Assignee: Lantao Jin
> Separate block manager heartbeat endpoint from driver endpoint
> --------------------------------------------------------------
>
> Key: SPARK-29298
> URL: https://issues.apache.org/jira/browse/SPARK-29298
> Project: Spark
> Issue Type: Improvement
> Components: Spark Core
> Affects Versions: 3.0.0
> Reporter: Lantao Jin
> Assignee: Lantao Jin
> Priority: Major
>
> Executor's heartbeat will send synchronously to BlockManagerMaster to let it know that the block manager is still alive. In a heavy cluster, it will timeout and cause block manager re-register unexpected.
> This improvement will separate a heartbeat endpoint from the driver endpoint. In our production environment, this is really helpful to prevent executors from unstable up and down.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org