-
Notifications
You must be signed in to change notification settings - Fork 44
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
old workers never die. #1
Comments
From what I've read in node's api documentation, the disconnect event may fire without the worker exiting if the worker is busy. But otherwise,
I tried using the |
This works - the workers are now cleaned up. |
Great, closing the issue. The fixed has been published on npm (0.1.5) |
Hi,
When I signal the master using SIGUSR2, new workers are started but the old ones never die.
What I think is happening is that the worker.disconnect() call is generating a disconnect event that clears the timeout before it has a chance to execute. Am I reading this correct?
I am running node 0.10.0, so it could be that this event wasn't generated in your version of node?
The text was updated successfully, but these errors were encountered: