From 713db4026b20a4dafcdee831b85fa1146334a56d Mon Sep 17 00:00:00 2001 From: Spencer Brody Date: Tue, 14 Aug 2012 12:30:28 -0300 Subject: [PATCH] Cluster metadata goes read-only, not user data --- source/release-notes/2.2.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/source/release-notes/2.2.txt b/source/release-notes/2.2.txt index 2d8ce849823..c745885ba9a 100644 --- a/source/release-notes/2.2.txt +++ b/source/release-notes/2.2.txt @@ -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