Docs Menu

Docs HomeDevelop ApplicationsMongoDB Manual

db.collection.reIndex()

On this page

  • Definition
  • Compatibility
  • Behavior
db.collection.reIndex()

Deprecated since version 6.0.

Attempting to run the db.collection.reIndex() method writes a warning message to the log.

Important

mongosh Method

This page documents a mongosh method. This is not the documentation for database commands or language-specific drivers, such as Node.js.

For the database command, see the reIndex command.

For MongoDB API drivers, refer to the language-specific MongoDB driver documentation.

For the legacy mongo shell documentation, refer to the documentation for the corresponding MongoDB Server release:

mongo shell v4.4

The db.collection.reIndex() drops all indexes on a collection and recreates them. This operation may be expensive for collections that have a large amount of data and/or a large number of indexes.

Warning

This method is available in deployments hosted in the following environments:

  • MongoDB Atlas: The fully managed service for MongoDB deployments in the cloud

Note

This command is not supported in M0, M2, and M5 clusters. For more information, see Unsupported Commands.

For MongoDB 5.0 or later, db.collection.reIndex() may only be run on standalone instances.

Changed in version 4.2.2.

For MongoDB 4.2.2 and later, db.collection.reIndex() obtains an exclusive (W) lock on the collection and blocks other operations on the collection until it completes.

For more information on locking in MongoDB, see FAQ: Concurrency.

Tip

See also:

←  db.collection.mapReduce()db.collection.remove() →