Skip to content

Commit cc444ad

Browse files
author
Sam Kleinman
committed
merge: DOCS-153
2 parents ef800a1 + 64bdf6d commit cc444ad

File tree

3 files changed

+16
-2
lines changed

3 files changed

+16
-2
lines changed

source/administration/sharding-architectures.txt

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -166,3 +166,7 @@ potential failure scenarios and available resolutions:
166166
splits <sharding-procedure-create-split>`. Replace the config server
167167
as soon as possible. If all multiple config databases become
168168
unavailable, the cluster can become inoperable.
169+
170+
.. note::
171+
172+
All config servers must be running when you first set up a shard cluster.

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:

source/core/sharding.txt

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -334,6 +334,10 @@ database. MongoDB only writes data to the config server to:
334334

335335
- migrate a chunk between shards.
336336

337+
Additionally, all config servers must be available on initial setup
338+
of a shard cluster, each :program:`mongos` instance must be able
339+
to write to the ``config.version`` collection.
340+
337341
If one or two configuration instances become unavailable, the
338342
cluster's metadata becomes *read only*. It is still possible to read
339343
and write data from the shards, but no chunk migrations or splits will

0 commit comments

Comments
 (0)