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.
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
Add fail_hard decorator for worker methods #6210
Add fail_hard decorator for worker methods #6210
Changes from 6 commits
6cbc05e
6eeac6b
97511ed
73471b2
b2fa15b
a991d84
b33b411
43b2962
a0721aa
b59ccd0
a08b5dd
e1c7447
a0b6f10
ebe8886
a1399a1
0505df8
50c31ef
96f7bd2
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Once the decorator is here, what's the point of having this block anymore?
distributed/distributed/worker.py
Lines 1201 to 1210 in 198522b
The decorator is going to close the worker as soon as the
finally
block completes. So what's the point of trying to reconnect if we're going to close either way? These seem like opposing behaviors.I think we want to either remove the try/except entirely from
handle_scheduler
(because all we want to do on error is close the worker, and@fail_hard
will do that for us anyway), or not use@fail_hard
here, if we do in fact still want to reconnect in the face of errors.