Repository navigation
Scheduler SIGTERM Handler #461
Description
Activity
- changed the title
[-]Scheduler SIGTERM/SIGINT Handler[/-][+]Scheduler SIGTERM Handler[/+]on May 8, 2025 I just found the same issue because docker wasn't able to properly stop the container using the default SIGINT signal. It just waits for the timeout and hard kills it after the configured timeout.
Reacted by Lryan
I noticed that the scheduler does not have a handler set for sigterm, which leads to the scheduler as a pid 1 process not properly handling the sigterm signals sent by the kube to exit correctly when I deploy the scheduler in a container alone.
Actually, sigint can be captured, but sigterm can not, and should probably be set explicitly.
Is it possible to set the signal handler for taskiq scheduler just like worker?