Skip to content

Update 2.4-upgrade.txt #715

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

Closed
wants to merge 1 commit into from
Closed

Update 2.4-upgrade.txt #715

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
11 changes: 7 additions & 4 deletions source/release-notes/2.4-upgrade.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -61,8 +61,9 @@ metadata in any other way.
The upgraded config database will require more storage space than
before, though this storage increase represents a fraction of the
current config database size. The additional storage requirement
will be less for deployments that have run with 2.2 for a
non-trivial period of time. See
will be much less for deployments that have run with 2.2 for a
non-trivial period of time, but, as always, pre-allocation of
data files could be triggered. See
:ref:`faq-tools-for-measuring-storage-use` for more information.

.. _2.4-upgrade-meta-data:
Expand Down Expand Up @@ -93,7 +94,9 @@ procedure.
#. Start a single 2.4 :program:`mongos` process with
:setting:`configdb` pointing to the sharded cluster's :ref:`config
servers <sharding-config-server>` and with the :option:`--upgrade
<mongos --upgrade>` option. You can upgrade an existing
<mongos --upgrade>` option. The upgrade process happens pre :option:`--fork`.

You can upgrade an existing
:program:`mongos` instance to 2.4 or you can start a new `mongos`
instance that can reach all config servers if you need to avoid
reconfiguring a production :program:`mongos`.
Expand Down Expand Up @@ -176,7 +179,7 @@ incompatibilities in future versions of MongoDB.

.. _upgrade-cluster-resync:

Resync after a Network Interruption
Resync after a Critical Section Interruption
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

During the short critical section of the upgrade that applies changes
Expand Down