[WIP][SPARK-17610][CORE][SCHEDULER]The failed stage caused by FetchFailed may never be resubmitted #15176
Conversation
This file contains 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
|
Test build #65707 has finished for PR 15176 at commit
|
WangTaoTheTonic
changed the title
|
after second glimpse, I found this current behavior will not cause problems because |
|
I will close this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What changes were proposed in this pull request?
The improper time order in handling failed task caused by FetchFailed may cause corresponding stage not being resubmitted ever. For details, see: https://issues.apache.org/jira/browse/SPARK-17610
How was this patch tested?
manual tests.