From f75d54607b29f991cfeed270c449335438c43ef6 Mon Sep 17 00:00:00 2001 From: Jeremiah Senkpiel Date: Fri, 28 Aug 2015 17:26:07 -0400 Subject: [PATCH] doc: clarify cluster behaviour with no workers Fixes: https://github.com/nodejs/node/issues/1239 Ref: 41b75ca9263f368db790fbdcc3963bb1a8c5cb7e PR-URL: https://github.com/nodejs/node/pull/2606 Reviewed-By: bnoordhuis - Ben Noordhuis --- doc/api/cluster.markdown | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/doc/api/cluster.markdown b/doc/api/cluster.markdown index 7cd079c04052fe..ea3d5ec2309256 100644 --- a/doc/api/cluster.markdown +++ b/doc/api/cluster.markdown @@ -99,9 +99,10 @@ for things like sessions and login. Because workers are all separate processes, they can be killed or re-spawned depending on your program's needs, without affecting other workers. As long as there are some workers still alive, the server will -continue to accept connections. io.js does not automatically manage the -number of workers for you, however. It is your responsibility to manage -the worker pool for your application's needs. +continue to accept connections. If no workers are alive, existing connections +will be dropped and new connections will be refused. io.js does not +automatically manage the number of workers for you, however. It is your +responsibility to manage the worker pool for your application's needs. ## cluster.schedulingPolicy