[dask] Prevent the training from hang due to aborted worker. - #10985
Merged
Merged
Conversation
| "This is likely caused by one of the workers died and Dask " | ||
| "re-scheduled a different one. Resilience is not yet supported." | ||
| ) | ||
| return [func(*args, **kwargs)] |
Contributor
There was a problem hiding this comment.
Will the functions that run on existing workers wait indefinitely for the dead worker to appear, or will they start failing at some point?
Member
Author
There was a problem hiding this comment.
They will fail as they poll their peers. Also, the poll itself has a timeout.
wphicks
approved these changes
Nov 7, 2024
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
3 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.
Set
allow_other_workers=Trueinclient.submit. See code comments for the rationale.