-
Notifications
You must be signed in to change notification settings - Fork 762
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
Terminate Worker/Queue #25
Comments
I tried this but with no luck... the work is still running:
|
The worker has shutdown to 1... so shouldn't it kill the process?
|
Looks like inside the loop $this doesn't get update at all..... |
So in the Resque_Worker I changed the shutdown function to:
Now things work as expected. I'll update the other functions too and send a pull request. |
Hi, Sorry, I haven't had much time recently to have a look over this. I think the problem with a proposed fix like this is that it's likely to kill all of the workers on the same box. If you spawn multiple workers, In fact, I'm curious as to why you're having problems with the current method. Are you trying to stop workers outside of the context of php-resque? If so, you should be able to send them the SIGQUIT from anything else, and they should shutdown after the current job has been processed. |
No problem.... Yee that's what it ended up doing... SIGQUIT works just fine :) I do have one other question about finding the correct pid, there doesn't seem to find a worker(s) by their queue name. You either have to find all or find by the exact name... is there a reason for this? |
Hi,
Is it possible to grab a queue/worker by name and stop (kill) it?
Many thanks,
CJ
The text was updated successfully, but these errors were encountered: