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 2021/02/24 05:06:00 UTC
[jira] [Resolved] (SPARK-34245) Master may not remove the finished
executor when Worker fails to send ExecutorStateChanged
[ https://issues.apache.org/jira/browse/SPARK-34245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Wenchen Fan resolved SPARK-34245.
---------------------------------
Fix Version/s: 3.2.0
Resolution: Fixed
Issue resolved by pull request 31348
[https://github.com/apache/spark/pull/31348]
> Master may not remove the finished executor when Worker fails to send ExecutorStateChanged
> ------------------------------------------------------------------------------------------
>
> Key: SPARK-34245
> URL: https://issues.apache.org/jira/browse/SPARK-34245
> Project: Spark
> Issue Type: Improvement
> Components: Deploy, Spark Core
> Affects Versions: 2.4.7, 3.0.1, 3.2.0, 3.1.1
> Reporter: wuyi
> Assignee: wuyi
> Priority: Major
> Fix For: 3.2.0
>
>
> If the Worker fails to send ExecutorStateChanged to the Master due to some errors, e.g., temporary network error, then the Master can't remove the finished executor normally and think the executor is still alive. In the worst case, if the executor is the only one executor for the application, the application can get hang.
>
--
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