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

Dead workers should be cleaned up on boot #227

Closed
mspanc opened this issue Jan 3, 2017 · 1 comment
Closed

Dead workers should be cleaned up on boot #227

mspanc opened this issue Jan 3, 2017 · 1 comment

Comments

@mspanc
Copy link

mspanc commented Jan 3, 2017

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:

zrzut ekranu z 2017-01-03 14-58-27

vault:<0.3125.0> and vault:<0.3704.0> were launched prior to reboot

@akira
Copy link
Owner

akira commented Jan 6, 2017

OK, this is a known issue, will need to look into a fix.

akira added a commit that referenced this issue Feb 23, 2017
When a node dies, stats are not cleaned up and workers can appear busy. To fix this,
cleanup stats for a host on boot.
Fixes #235 / #227
akira added a commit that referenced this issue Feb 23, 2017
When a node dies, stats are not cleaned up and workers can appear busy. To fix this,
cleanup stats for a host on boot.

Fixes #235 / #227
@akira akira closed this as completed Feb 23, 2017
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

2 participants