Docs Menu
Docs Home
/
MongoDB Manual
/ / /

Change Sharded Cluster to WiredTiger

Note

You must upgrade to WiredTiger. MongoDB removed the deprecated MMAPv1 storage engine in version 4.2.

Use this tutorial to update MongoDB 4.0 sharded clusters to use WiredTiger.

For earlier versions of MongoDB:

  • To convert a 3.6 sharded cluster that uses MMAPv1, see the MongoDB 3.6 manual.

  • To convert a 3.4 sharded cluster that uses MMAPv1, see the MongoDB 3.4 manual.

  • To convert a 3.2 sharded cluster that uses MMAPv1, see the MongoDB 3.2 manual.

If you change the host or port of any shard, you must update the shard configuration as well.

The "majority" read concern, available for WiredTiger, is enabled by default. However, if you have a three-member shard replica set with a primary-secondary-arbiter (PSA) architecture, you can disable "majority" read concern for that shard replica set. Disabling "majority" for a three member PSA architecture avoids possible cache-pressure build up.

Note

Disabling "majority" read concern has no effect on change streams availability.

Disabling "majority" read concern prevents collMod commands which modify an index from rolling back. If such an operation needs to be rolled back, you must resync the affected nodes with the primary node.

Disabling "majority" read concern affects support for transactions on sharded clusters. Specifically:

  • A transaction cannot use read concern "snapshot" if the transaction involves a shard that has disabled read concern "majority".

  • A transaction that writes to multiple shards errors if any of the transaction's read or write operations involves a shard that has disabled read concern "majority".

However, it does not affect transactions on replica sets. For transactions on replica sets, you can specify read concern "majority" (or "snapshot" or "local" ) for distributed transactions even if read concern "majority" is disabled.

For more information on PSA architecture and read concern "majority", see Primary-Secondary-Arbiter Replica Sets.

You must be using MongoDB version 3.0 or greater in order to use the WiredTiger storage engine. If using an earlier MongoDB version, you must upgrade your MongoDB version before proceeding to change your storage engine. To upgrade your MongoDB version, refer to the appropriate version of the manual.

MongoDB binaries, mongod and mongos, bind to localhost by default.

Starting in version 3.4, config servers must be deployed as replica sets (CSRS). As such, version 3.4+ config servers already use the WiredTiger storage engine.

With the WiredTiger storage engine, using XFS for data bearing nodes is recommended on Linux. For more information, see Kernel and File Systems.

Once upgraded to WiredTiger, your WiredTiger deployment is not subject to the following MMAPv1-only restrictions:

MMAPv1 Restrictions
Short Description
Number of Namespaces
For MMAPv1, the number of namespaces is limited to the size of the namespace file divided by 628.
Size of Namespace File
For MMAPv1, namespace files can be no larger than 2047 megabytes.
Database Size
The MMAPv1 storage engine limits each database to no more than 16000 data files.
Data Size
For MMAPv1, a single mongod instance cannot manage a data set that exceeds maximum virtual memory address space provided by the underlying operating system.
Number of Collections in a Database
For the MMAPv1 storage engine, the maximum number of collections in a database is a function of the size of the namespace file and the number of indexes of collections in the database.

For each replica set shard, to change the storage engine to WiredTiger:

Update the secondary members one at a time:

1

In mongosh, shut down the secondary.

use admin
db.shutdownServer()
2

Prepare a data directory for the new mongod instance that will run with the WiredTiger storage engine. mongod must have read and write permissions for this directory. You can either delete the contents of the stopped secondary member's current data directory or create a new directory entirely.

mongod with WiredTiger will not start with data files created with a different storage engine.

3

Remove any MMAPv1 configuration options from the mongod instance configuration.

4

Start mongod, specifying wiredTiger as the --storageEngine and the prepared data directory for WiredTiger as the --dbpath.

Specify additional options as appropriate, such as --bind_ip.

Warning

Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.

Since no data exists in the --dbpath, the mongod will perform an initial sync. The length of the initial sync process depends on the size of the database and network connection between members of the replica set.

You can also specify the options in a configuration file. To specify the storage engine, use the storage.engine setting.

Repeat the steps for the remaining secondary members, updating them one at a time.

Once all the secondary members have been upgraded to WiredTiger, connect mongosh to the primary and use rs.stepDown() to step down the primary and force an election of a new primary.

rs.stepDown()

When the primary has stepped down and become a secondary, update the secondary to use WiredTiger as before:

1

In mongosh, shut down the secondary.

use admin
db.shutdownServer()
2

Prepare a data directory for the new mongod instance that will run with the WiredTiger storage engine. mongod must have read and write permissions for this directory. You can either delete the contents of the stopped secondary member's current data directory or create a new directory entirely.

mongod with WiredTiger will not start with data files created with a different storage engine.

3

Remove any MMAPv1 configuration options from the mongod instance configuration.

4

Start mongod, specifying wiredTiger as the --storageEngine and the prepared data directory for WiredTiger as the --dbpath.

Specify additional options as appropriate, such as --bind_ip.

Warning

Before binding to a non-localhost (e.g. publicly accessible) IP address, ensure you have secured your cluster from unauthorized access. For a complete list of security recommendations, see Security Checklist. At minimum, consider enabling authentication and hardening network infrastructure.

Since no data exists in the --dbpath, the mongod will perform an initial sync. The length of the initial sync process depends on the size of the database and network connection between members of the replica set.

You can also specify the options in a configuration file. To specify the storage engine, use the storage.engine setting.

Repeat the procedure for the other shards.

← Change Replica Set to WiredTiger