-
Notifications
You must be signed in to change notification settings - Fork 28.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[SPARK-32003][CORE] When external shuffle service is used, unregister outputs for executor on fetch failure after executor is lost #28848
Closed
Commits on Jul 15, 2020
-
[SPARK-32003][CORE] Unregister outputs for executor on fetch failure …
…after executor is lost If an executor is lost, the `DAGScheduler` handles the executor loss by removing the executor but does not unregister its outputs if the external shuffle service is used. However, if the node on which the executor runs is lost, the shuffle service may not be able to serve the shuffle files. In such a case, when fetches from the executor's outputs fail in the same stage, the `DAGScheduler` again removes the executor and by right, should unregister its outputs. It doesn't because the epoch used to track the executor failure has not increased. We track the epoch for failed executors that result in lost file output separately, so we can unregister the outputs in this scenario.
Configuration menu - View commit details
-
Copy full SHA for e36b442 - Browse repository at this point
Copy the full SHA e36b442View commit details -
[SPARK-32003] Update fileLostEpoch.
I inadvertently left out a line when transferring code. The fileLostEpoch needs to be updated with an entry for the failed executor with lost output. Adopted suggestions from wuyi and attilapiros.
Configuration menu - View commit details
-
Copy full SHA for fca8a6e - Browse repository at this point
Copy the full SHA fca8a6eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 973e385 - Browse repository at this point
Copy the full SHA 973e385View commit details -
Configuration menu - View commit details
-
Copy full SHA for b9e55a4 - Browse repository at this point
Copy the full SHA b9e55a4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 06ea411 - Browse repository at this point
Copy the full SHA 06ea411View commit details -
Configuration menu - View commit details
-
Copy full SHA for 17393eb - Browse repository at this point
Copy the full SHA 17393ebView commit details -
Configuration menu - View commit details
-
Copy full SHA for d450c3e - Browse repository at this point
Copy the full SHA d450c3eView commit details -
Configuration menu - View commit details
-
Copy full SHA for a8e619c - Browse repository at this point
Copy the full SHA a8e619cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1923598 - Browse repository at this point
Copy the full SHA 1923598View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0e00862 - Browse repository at this point
Copy the full SHA 0e00862View commit details
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.