Skip to content

DOCS-153 all config servers must be up when initializing a shard cluster #181

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Sep 5, 2012
Merged

DOCS-153 all config servers must be up when initializing a shard cluster #181

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
9993df8
DOCS-153 add note about all config servers needing to be up on initia…
Sep 5, 2012
64bdf6d
DOCS-153 all config servers must be up to init cluster
Sep 5, 2012
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions source/administration/sharding-architectures.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -166,3 +166,7 @@ potential failure scenarios and available resolutions:
splits <sharding-procedure-create-split>`. Replace the config server
as soon as possible. If all multiple config databases become
unavailable, the cluster can become inoperable.

.. note::

All config servers must be running when you first set up a shard cluster.
10 changes: 8 additions & 2 deletions source/administration/sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,6 +59,10 @@ more detail or use the following procedure as a quick starting point:
:doc:`command line </reference/mongod>` and :doc:`configuration
file </reference/configuration-options>` options are available for config
server instances.

.. note::

All config servers must be running when you first set up a shard cluster.

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

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

Do not use only a single config server for production deployments.
Consider deploying a single config server for testing.
immediately. The following process shows how to upgrade from one to
Consider deploying a single config server only for testing.
You should upgrade to three config servers immediately if you are
shifting to production.
The following process shows how to upgrade from one to
three config servers.

#. Shut down all existing MongoDB processes. This includes:
Expand Down
4 changes: 4 additions & 0 deletions source/core/sharding.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -334,6 +334,10 @@ database. MongoDB only writes data to the config server to:

- migrate a chunk between shards.

Additionally, all config servers must be available on initial setup
of a shard cluster, each :program:`mongos` instance must be able
to write to the ``config.version`` collection.

If one or two configuration instances become unavailable, the
cluster's metadata becomes *read only*. It is still possible to read
and write data from the shards, but no chunk migrations or splits will
Expand Down