Handle errant workers when another worker has data #1853
Merged
Conversation
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
Previously we would fail in the following situation:
1. A and B both data
2. C tries to get data from A
3. A fails during this transfer
4. The scheduler goes to clean things up and gets confused because
someone (B) still has the data
The fix for this wasn't hard, but the test is a bit odd. It seems
that the subsequent communication from C to B fails, which I don't
yet understand.
Related to dask#1836
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.
Previously we would fail in the following situation:
someone (B) still has the data
The fix for this wasn't hard, but the test is a bit odd. It seems
that the subsequent communication from C to B fails, which I don't
yet understand.
Related to #1836