-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
any to shutdown a worker without warm? #242
Comments
|
I'm closing old issues. If this issue still applies and requires my attention, I ask you kindly to re-open it or file a new issue. Thanks. |
I have the same issue, when i stop
|
Same problem here. |
Same problem here, I work around it by just issuing two |
docker-compose run worker-service |
I have the same problem, but I start rq as a background process, so italomaia's fix does not apply. Is there a way to work around this?
|
yes, just send it a standard kill signal.
then take the process id (the second number) and execute
|
I use supervisor to manage my rq worker
and my supervisor conf is like this
But when I restart use
supervisorctl -c /etc/supervisord.conf update re-upload:*
It always tell me the worker name has used
The text was updated successfully, but these errors were encountered: