Skip to content

Clarify that when a config server is down, cluster metadata goes read-only, not regular user data #120

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 1 commit into from
Aug 14, 2012
Merged

Clarify that when a config server is down, cluster metadata goes read-only, not regular user data #120

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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: 2 additions & 2 deletions source/release-notes/2.2.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -83,8 +83,8 @@ procedure:

- Upgrade all of the :program:`mongod` config server instances *one at
a time*. When you have *less* than *three* config servers active,
the cluster will be read-only which will prevent (and abort) all
chunk migrations and chunk splits.
the cluster metadata will be read-only which will prevent (and abort)
all chunk migrations and chunk splits.

- Upgrade all remaining cluster components. Use the :ref:`upgrade
procedure for replica sets <2.2-upgrade-replica-set>` for each of
Expand Down