Skip to content

Commit d60535b

Browse files
author
Sam Kleinman
committed
upgrade correction
1 parent 6aa79ea commit d60535b

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

source/release-notes/2.4-upgrade.txt

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -6,15 +6,15 @@ Upgrade MongoDB 2.2 to 2.4
66

77
Only upgrade sharded clusters to 2.4 if all members of the cluster are
88
currently running instances of 2.2. The only supported upgrade path
9-
for sharded clusters running 2.0 is via 2.2.
9+
for sharded clusters running 2.0 is via 2.2.
1010

1111
.. _upgrade-cluster-upgrade:
1212

1313
Upgrade a Sharded Cluster from MongoDB 2.2 to MongoDB 2.4
1414
---------------------------------------------------------
1515

1616
Upgrading a :term:`sharded cluster` from MongoDB version 2.2 to 2.4
17-
(or 2.3) requires that you run a 2.4 :ref:`config server <sharding-config-server>`
17+
(or 2.3) requires that you run a 2.4 :program:`mongos`
1818
with the :option:`--upgrade <mongos --upgrade>` option, described in
1919
this procedure. The upgrade process does not require downtime.
2020

@@ -30,8 +30,8 @@ collection metadata. For example, you cannot perform operations that
3030
add shards, drop databases, or drop collections, or modify the
3131
metadata in any other way.
3232

33-
.. warning::
34-
33+
.. warning::
34+
3535
Once you upgrade to 2.4 and complete the upgrade procedure **do
3636
not** use 2.0 :program:`mongod` and :program:`mongos` processes in
3737
your cluster. 2.0 process may re-introduce old metadata formats

0 commit comments

Comments
 (0)