On Sat, Nov 16, 2013 at 9:22 PM, Evan <evantah...@gmail.com> wrote: > @matt I guess it really depends on your application logic. My > understanding of > cluster.disconnect<http://nodejs.org/api/cluster.html#cluster_cluster_disconnect_callback> > is > that the worker/child will instantly close all open sockets/pipes/etc. > That means that if you have a client mid-request, that request will > timeout. I don't think the client will see a true connection failure, as > they are technically connecting `via` the cluster master, and the socket > (as far as they can see) will remain open. This kind of thing gets > dangerous if you are mid-database operation or similar. >
Nope, that's not how worker.disconnect() works. It just tells the master to not send any more connections to that child, allowing it to gracefully exit. Now of course if the child has some other reason to stick around (a setInterval or an outbound connection somewhere) then it will do so, but you need to take care of that in any system which supports graceful restarts. Matt. -- -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to nodejs@googlegroups.com To unsubscribe from this group, send email to nodejs+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en --- You received this message because you are subscribed to the Google Groups "nodejs" group. To unsubscribe from this group and stop receiving emails from it, send an email to nodejs+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
