[ https://issues.apache.org/jira/browse/SPARK-32198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Holden Karau resolved SPARK-32198. ---------------------------------- Fix Version/s: 3.1.0 Target Version/s: 3.1.0 Resolution: Fixed > 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 > Assignee: Devesh Agrawal > Priority: Major > Fix For: 3.1.0 > > > 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-unsubscr...@spark.apache.org For additional commands, e-mail: issues-h...@spark.apache.org