Skip to content

Commit 64bdf6d

Browse files
author
Ed Costello
committed
DOCS-153 all config servers must be up to init cluster
1 parent 9993df8 commit 64bdf6d

File tree

2 files changed

+8
-0
lines changed

2 files changed

+8
-0
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/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)