Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

signal behavior #7

Open
mguterl opened this issue Jan 31, 2011 · 3 comments
Open

signal behavior #7

mguterl opened this issue Jan 31, 2011 · 3 comments

Comments

@mguterl
Copy link

mguterl commented Jan 31, 2011

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.

@mguterl
Copy link
Author

mguterl commented Feb 1, 2011

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

@sandbox
Copy link

sandbox commented Jul 7, 2011

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

@jeremy
Copy link

jeremy commented Feb 27, 2018

Fixed by stulentsev#2 (that's the new primary GitHub repository as well)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants