In real life, we need sometime to update application on production servers. A good practice is to do such things without service interruption. Usual solution is binding new processes to the same address, and disabling old ones to accept new connections. In case of websockets, old processes can additionally signal clients to reconnect.
Full algorythm is well described in nginx docs http://nginx.org/en/docs/control.html#upgrade Does it worth to create issue with request or such functionality is specific for my needs? The second question is about software RR scheduler, that i found in cluster sources. Why it was was prefered over system's one? Will scheduler IPC add noticeable latency for server replies or not? -- -- 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 [email protected] To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
