You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Devesh Agrawal (Jira)" <ji...@apache.org> on 2020/07/06 20:28:00 UTC
[jira] [Updated] (SPARK-32198) Don't fail running jobs when
decommissioned executors finally go away
[ https://issues.apache.org/jira/browse/SPARK-32198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Devesh Agrawal updated SPARK-32198:
-----------------------------------
Shepherd: Holden Karau
> Don't fail running jobs when decommissioned executors finally go away
> ---------------------------------------------------------------------
>
> Key: SPARK-32198
> URL: https://issues.apache.org/jira/browse/SPARK-32198
> Project: Spark
> Issue Type: Sub-task
> Components: Spark Core
> Affects Versions: 3.1.0
> Reporter: Devesh Agrawal
> Priority: Major
>
> When a decommissioned executor is finally lost, its death shouldn't fail running jobs.
> A decommissioned executor will eventually die, and in response to its heartbeat failure we will generate a `SlaveLost` message. This SlaveLost message should be treated specially for decommissioned executors: It should not be deemed that this loss is due to the running application. Decommissioning is an exogenous event and the running application shouldn't be penalized for it.
>
>
--
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