fix: SIGINT worker processes when process_manager starts #362
Conversation
This file contains 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
Without this change, I found that workers could get stuck on a long-running task. Worker processes are sent a SIGINT, and then that signal is handled appropriately to exit the prefetcher & runner
|
I note that tasks cancelled in this way have their result returned as error = KeyboardInterrupt. In my own application, I have a middleware that re-kicks these tasks when the worker next starts. |
s3rius
approved these changes
Sep 6, 2024
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.
Without this change, I found that workers could get stuck on a long-running task. Worker processes are sent a SIGINT, and then that signal is handled appropriately to exit the prefetcher & runner.
Is this appropriate as general purpose behaviour, and if not, would it make sense as a command-line option?