Repository navigation
fix(core): Overhaul worker shutdown to make sure all tasks are executed before terminating #1704
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
Open
maciejdudko
wants to merge
7
commits into
main
Choose a base branch
from
maciejdudko/poller-shutdown-fix
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+2,056
−1,144
Open
Changes from all commits
Commits
Show all changes
7 commits
Select commit
Hold shift + click to select a range
d1e5a27
fix(core): Overhaul worker shutdown to make sure all tasks are execut…
maciejdudko a7fd763
Changelog and formatting
maciejdudko d1e4a71
Addressed PR comments
maciejdudko b3b3324
Merge branch 'main' into maciejdudko/poller-shutdown-fix
maciejdudko 50d2326
Fixes after merge
maciejdudko 8e5998a
Merge branch 'main' into maciejdudko/poller-shutdown-fix
maciejdudko fa82312
Merge branch 'main' into maciejdudko/poller-shutdown-fix
maciejdudko File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
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.
I think we can simplify this a fair amount. Right now it's easy to forget to use the semaphore properly and we could solve that by reversing the way it works. EX: If anyone forgets to pass in an attempt semaphore, that call can get interrupted immediately.
Rather than initializing it with a permit, we should init it with 0, then the permit gets added in
TonicErrorHandler::wait_retryand every attempt after the first attempt acquires in the gRPC interceptor but wait to forget it until just before running.Here's an AI sketch of the changes:
make_future_retry takes an FnMut, so mutating the flag inside the closure is fine.
wait_retry already does sem.add_permits(1) before returning WaitRetry. The ForwardError and success paths leave the count at 0, as they do now.
Putting the poll branch first also fixes another issue: a poll that has just completed wins the tie. That's safe in graceful mode, because the waiting interrupt branch is first in the semaphore's FIFO queue. When a retry adds a permit, it goes to the interrupt branch, not to the next attempt.
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.
The other thing we can do I think is eliminate
RetryCallbackentirely, and re-use the semaphore to deal with the same thing:It does mean we will now possibly wait for an in-flight
ShutdownWorkerrpc to finish, but, that's totally fine.