seayoun opened a new pull request #26975: Stage retry and executor crash cause app hung up forever URL: https://github.com/apache/spark/pull/26975 ### **What changes were proposed in this pull request?** Fix a bug can cause app hung. The bug code analysis and discuss here: https://issues.apache.org/jira/browse/SPARK-30325 The bugs occurs in the corer case as follows: 1. The stage occurs for fetchFailed and some task hasn't finished, scheduler will resubmit a new stage as retry with those unfinished tasks. 2. The unfinished task in origin stage finished and the same task on the new retry stage hasn't finished, it will mark the task partition on the new retry stage as succesuful. 3. The executor running those 'successful task' crashed, it cause taskSetManager run executorLost to rescheduler the task on the executor, here will cause copiesRunning decreate 1 twice, beause those 'successful task' are not finished, the variable copiesRunning will decreate to -1 as result. 4. 'dequeueTaskFromList' will use copiesRunning equal 0 as reschedule basis when rescheduler tasks, and now it is -1, can't to reschedule, and the app will hung forever. Kill tasks which succeeded in origin stage when new retry stage has started the same task and hasn't finished. This can alse decreate stage run time, resouce cost. ### **Why are the changes needed?** This will cause app hung up. ### **Does this PR introduce any user-facing change?** No ### **How was this patch tested?**
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org For additional commands, e-mail: reviews-h...@spark.apache.org
