[SPARK-24931][CORE]CoarseGrainedExecutorBackend send wrong 'Reason' w…#21891
Closed
bingbai0912 wants to merge 2 commits into
Closed
[SPARK-24931][CORE]CoarseGrainedExecutorBackend send wrong 'Reason' w…#21891bingbai0912 wants to merge 2 commits into
bingbai0912 wants to merge 2 commits into
Conversation
…hen executor exits which leading to job failed.
|
Can one of the admins verify this patch? |
…ds with special character(s)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
TaskSetManager## What changes were proposed in this pull request?
When CoarseGrainedExecutorBackend find the executor not available, it will send a "RemoveExecutor" message of "ExecutorExited" instead "ExecutorLossReason". So it call tell driver whether is the executor "exitCausedByApp" which should be false. So when dirver(TaskSetManager) can "handleFailedTask" correctly to avoid task failed time up to the "maxTaskFailures" and finally cause job failed.
How was this patch tested?
tested in my own cluster