Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Send SIGTERM after SIGINT
See original GitHub issueIssue Description
Hi again!!!
Usually, when we want to kill a process, we’ll first try to gracefully kill it. If it refuses to die, we may send another signal to force it to die.
Currently in huey, if we send a SIGINT to consumer, it’ll set the stop flag and try to join the workers. If the workers refuse to die, the consumer has no choice but to wait. If we send another SIGTERM to consumer, it won’t work because the corresponding signal handler only sets some variables. There doesn’t seem to be a way to tell the consumer to not wait anymore and the second SIGTERM signal may be meaningless.
I think it’ll be useful if huey provides the option that users can first try to gracefully kill the consumer, and also ungracefully kill the consumer if it won’t die.
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Pushed 2.1.3 with this change.
Ah, I guess it is behaving differently with processes than when using threads. I just made a test of using TERM with a blocked worker and indeed – the worker does not shut down immediately. Let me look into it.