-
Notifications
You must be signed in to change notification settings - Fork 182
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
Dead workers should be cleaned up on boot #227
Comments
OK, this is a known issue, will need to look into a fix. |
Closed
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I use exq 0.8.2 with elixir 1.3.4 on heroku. I use custom module to set up node identifier so it is not randomized by heroku after application restarts.
I have found out that if I deploy the app which results in killing the whole process, the processes that were active during kill are not removed from the queue after reboot, effectively blocking slots for new workers.
See screenshot:
vault:<0.3125.0> and vault:<0.3704.0> were launched prior to reboot
The text was updated successfully, but these errors were encountered: