Skip to content

Update source/release-notes/2.2.txt #193

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
Sep 6, 2012
Merged

Update source/release-notes/2.2.txt #193

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
38 changes: 15 additions & 23 deletions source/release-notes/2.2.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -80,41 +80,33 @@ procedure:
Upgrading a Shard Cluster
~~~~~~~~~~~~~~~~~~~~~~~~~

If your cluster uses authentication, use the following upgrade
procedure:
We recommend the following upgrade procedure for a sharded cluster:

- :ref:`disable the balancer <sharding-balancing-disable-temporally>`,

- Upgrade all :program:`mongos` instances *first*, in any order.

- Upgrade all of the :program:`mongod` config server instances *one at
a time*. When you have *fewer* than *three* config servers active,
the cluster metadata will be read-only which will prevent (and abort)
all chunk migrations and chunk splits.
a time* using the :ref:`stand alone <2.2-upgrade-standalone>` procedure.
When you have *fewer* than *three* config servers active, 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
- Upgrade all remaining cluster components, using the :ref:`upgrade
procedure for replica sets <2.2-upgrade-replica-set>` for each of
the shards and the :ref:`stand alone <2.2-upgrade-standalone>`
procedure for each of the config servers. You may upgrade the
components of your cluster in any order.
the shards.

If your cluster *does not* use authentication, you may upgrade the
components of the cluster in any order, using the :ref:`upgrade
procedure for replica sets <2.2-upgrade-replica-set>` for each of the
shards and the :ref:`stand alone <2.2-upgrade-standalone>` procedure
for each of the config servers.
- re-enable the balancer.

.. note::
If your cluster uses authentication, you must upgrade the components in
the order above. If your cluster does not use authentication, you can
upgrade the mongos instances, config servers, and shards in any order.

Balancing does not work in *mixed* 2.0 and 2.2 deployments. For the
best results:

- :ref:`disable the balancer <sharding-balancing-disable-temporally>`,
.. note::

- upgrade the :program:`mongos`, if using authentication,
Balancing does not currently work in *mixed* 2.0.x and 2.2.0 deployments.

- upgrade all :program:`mongod` instances, including all shard
components and configuration instances in the cluster, and

- re-enable the balancer.

Changes
-------
Expand Down