Skip to content

Add explanation on reIndex() fix typo on getIndexes #1110

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

Add explanation on reIndex() fix typo on getIndexes #1110

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
5 changes: 3 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 @@ -172,12 +172,13 @@ operations.

#. .. include:: /includes/fact-upgrade-sharded-cluster-prereq.rst

To check the version of your indexes, run :method:`~db.collectiongetIndexes()`.
To check the version of your indexes, run :method:`db.collection.getIndexes()`.

If any index **on the config database** is ``{v:0}``, you should drop that index using
:method:`dropIndex() <db.collection.dropIndex>`, and then rebuild it
with :method:`ensureIndex() <db.collection.ensureIndex>`. This does
not apply to indexes on other databases in the cluster.
not apply to indexes on other databases in the cluster. If the ``_id``
index needs to be upgraded to ``{v:1}`` use the :method:`reIndex() <db.collection.reIndex>`.

#. Turn off the :ref:`balancer <sharding-balancing-internals>` in the
:term:`sharded cluster`, as described in
Expand Down