You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When stopping an ofelia container, the running jobs do not receive a SIGTERM signal which would tell them the container is about to stop, instead it just waits for them to finish normally (which can take an undefined amount of time) then 10 seconds later docker SIGKILLs the ofelia container which prevents them from shutting down correctly and doing the cleanup that they should be doing, this is a problem for very long jobs
A SIGTERM would normally tell those jobs that they are about to stop and that they should save their current state, they otherwise loose the progress they made
Also while waiting for jobs to stop, new jobs are being picked up, which would also get killed without due process
PS: While the docker API currently does not support killing an exec, we can still create a new exec with the command kill -n 9 $execId, I would attempt a PR, but I have never touched go before
The text was updated successfully, but these errors were encountered:
Tofandel
changed the title
Cron jobs are killed with SIGKILL instead of SIGTERM
Cron jobs are not signaled SIGTERM on terminated and jobs are still started while waiting for termination
Jul 5, 2023
When stopping an ofelia container, the running jobs do not receive a
SIGTERM
signal which would tell them the container is about to stop, instead it just waits for them to finish normally (which can take an undefined amount of time) then 10 seconds later dockerSIGKILL
s the ofelia container which prevents them from shutting down correctly and doing the cleanup that they should be doing, this is a problem for very long jobsA
SIGTERM
would normally tell those jobs that they are about to stop and that they should save their current state, they otherwise loose the progress they madeAlso while waiting for jobs to stop, new jobs are being picked up, which would also get killed without due process
PS: While the docker API currently does not support killing an exec, we can still create a new exec with the command
kill -n 9 $execId
, I would attempt a PR, but I have never touched go beforeThe text was updated successfully, but these errors were encountered: