doc: clarify cluster behaviour with no workers

Fixes: #1239 Ref: 41b75ca PR-URL: #2606 Reviewed-By: bnoordhuis - Ben Noordhuis <[email protected]>
nodejs · Aug 31, 2015 · f75d546 · f75d546
1 parent bb24c4a
commit f75d546
Showing 1 changed file with 4 additions and 3 deletions.
diff --git 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