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
I, [2024-01-19T21:18:30.507015 #2608] INFO -- : received WINCH signal
I, [2024-01-19T21:18:30.507329 #2608] INFO -- : sent TERM signal to worker 2689
I, [2024-01-19T21:18:30.647926 #2689] INFO -- : performed UpdateInventoryLevelsJob [2e837034-35df-4573-b638-0fc7815bb547] from DelayedJob(urgent) with arguments: [], memory: 322 MB
I, [2024-01-19T21:18:30.650728 #2689] INFO -- : shut down worker 2689
D, [2024-01-19T21:18:30.940508 #2608] DEBUG -- : found terminated pid: 2689
Looking at the code, it seems like the signaler calls graceful_stop
When I start a job, then call
my workers teminate immediately and my job fails with a
SignalException SIGTERM
This is the key feature I'm looking for in this gem, deployments that won't interrupt running jobs.
The log shows
Looking at the code, it seems like the signaler calls graceful_stop
delayed_job_master/lib/delayed/master/core.rb
Lines 89 to 92 in c757a42
which dispatches TERM
delayed_job_master/lib/delayed/master/signaler.rb
Lines 25 to 30 in c757a42
and that kills the process
delayed_job_master/lib/delayed/master/signaler.rb
Lines 43 to 48 in c757a42
I might not be tracing this right.
My understanding of the graceful stop is that it would allow the job to complete before killing the process.
Is this working as intended?
The text was updated successfully, but these errors were encountered: