Skip to content

Update source/release-notes/2.4-upgrade.txt #695

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 source/release-notes/2.4-upgrade.txt #695

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
8 changes: 6 additions & 2 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 @@ -56,15 +56,19 @@ metadata in any other way.
your cluster. 2.0 process may re-introduce old metadata formats
into cluster metadata.

Also ensure you have sufficient space available on your config server before
starting the upgrade process. The information added during upgrade
will be only a fraction of the current config data size, but preallocation
of data files may cause suprising effects. See :ref:`what-tools-can-i-use-to-investigate-storage-use-in-mongodb`.

Sharded Cluster Upgrade Procedure
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Do not perform operations that modify metadata while performing this
procedure.

1. Turn off the :ref:`balancer <sharding-balancing-internals>` in the
:term:`sharded cluster`, as described in
:ref:`sharding-balancing-disable-temporally`.
:term:`sharded cluster`, as described in`:ref:`sharding-balancing-disable-temporally`.

#. Ensure there are no version 2.0 :program:`mongod` or
:program:`mongos` processes still active in the sharded
Expand Down