Skip to content

Commit 9993df8

Browse files
author
Ed Costello
committed
DOCS-153 add note about all config servers needing to be up on initial setup
also fix error (elided sentence) introduced in fc3b14f
1 parent 8f09ebe commit 9993df8

File tree

1 file changed

+8
-2
lines changed

1 file changed

+8
-2
lines changed

source/administration/sharding.txt

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,10 @@ more detail or use the following procedure as a quick starting point:
5959
:doc:`command line </reference/mongod>` and :doc:`configuration
6060
file </reference/configuration-options>` options are available for config
6161
server instances.
62+
63+
.. note::
64+
65+
All config servers must be running when you first set up a shard cluster.
6266

6367
#. Start a :program:`mongos` instance issuing the following command:
6468

@@ -889,8 +893,10 @@ For redundancy, all production :term:`shard clusters <shard cluster>` should
889893
deploy three config servers processes on three different machines.
890894

891895
Do not use only a single config server for production deployments.
892-
Consider deploying a single config server for testing.
893-
immediately. The following process shows how to upgrade from one to
896+
Consider deploying a single config server only for testing.
897+
You should upgrade to three config servers immediately if you are
898+
shifting to production.
899+
The following process shows how to upgrade from one to
894900
three config servers.
895901

896902
#. Shut down all existing MongoDB processes. This includes:

0 commit comments

Comments
 (0)