resque-multi-job-forks signal behavior

signal behavior

Open mguterl opened this issue 14 years ago • 3 comments

Can you clarify how resque workers should respond to signals when using resque-multi-job-forks?

I ask because it seems like my workers aren't responding to QUIT or if they are it is only after the fork time limit is reached.

Jan 31 '11 23:01 mguterl

After some experimentation, I can confirm that workers do not respond to QUIT until fork_job_limit_reached? returns true.

Feb 01 '11 17:02 mguterl

The child process also needs to be sent the signal call so that its @shutdown variable can be set.

I think it is assumed that the child only lives in these three lines https://github.com/defunkt/resque/blob/master/lib/resque/worker.rb#L129-L131

Jul 07 '11 23:07 sandbox

Fixed by https://github.com/stulentsev/resque-multi-job-forks/pull/2 (that's the new primary GitHub repository as well)

Feb 27 '18 02:02 jeremy