Docs Menu

Perform Maintenance on Replica Set Members

On this page

  • Overview
  • Procedure

Replica sets allow a MongoDB deployment to remain available during the majority of a maintenance window.

This document outlines the basic procedure for performing maintenance on each of the members of a replica set. Furthermore, this particular sequence strives to minimize the amount of time that the primary is unavailable and control the impact on the entire deployment.

Use these steps as the basis for common replica set operations, particularly for procedures such as upgrading to the latest version of MongoDB.

For each member of a replica set, starting with a secondary member, perform the following sequence of events, ending with the primary:

1

In mongosh, shut down the mongod instance:

db.shutdownServer()
2

At the operating system shell prompt restart mongod as a standalone instance.

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.

Always start mongod with the same user, even when restarting a replica set member as a standalone instance.

3

While the member is a standalone, use mongosh to perform maintenance:

mongo --port 27218
Important

While the member is a standalone, no writes are replicated to this member nor are writes on this member replicated to the other members of the replica set.

Ensure that any writes on this standalone do not conflict with oplog writes that will be applied to the member when it rejoins the replica set.

4

After performing all maintenance tasks, use the following procedure to restart the mongod as a member of the replica set on its usual port.

From mongosh, shut down the standalone server after completing the maintenance:

use admin
db.shutdownServer()

Restart the mongod instance as a replica set member with its original configuration; that is, undo the configuration changes made when starting as a standalone.

Tip

Be sure to remove the disableLogicalSessionCacheRefresh parameter.

For shard or config server members, be sure to remove the skipShardingConfigurationChecks parameter.

When it has started, connect mongosh to the restarted instance.

The secondary takes time to catch up to the primary. From mongosh, use the following command to verify that the member has caught up from the RECOVERING state to the SECONDARY state.

rs.status()
5
  1. To perform maintenance on the primary after completing maintenance tasks on all secondaries, connect mongosh to the primary and use rs.stepDown() to step down the primary and allow one of the secondaries to be elected the new primary. Specify a 300 second waiting period to prevent the member from being elected primary again for five minutes:

    rs.stepDown(300)

    After the primary steps down, the replica set will elect a new primary.

  2. Restart mongod as a standalone instance, making the following configuration updates.
  1. Perform maintentance task on the now standalone.

    Important

    While the member is a standalone, no writes are replicated to this member nor are writes on this member replicated to the other members of the replica set.

    Ensure that any writes on this standalone do not conflict with oplog writes that will be applied to the member when it rejoins the replica set.

  2. After performing all maintenance tasks, restart the mongod instance as a replica set member with its original configuration; that is, undo the configuration changes made when starting as a standalone.

    Tip

    Be sure to remove the disableLogicalSessionCacheRefresh parameter.

    For shard or config server members, be sure to remove the skipShardingConfigurationChecks parameter.

On this page

Give Feedback
© 2021 MongoDB, Inc.

About

  • Careers
  • Legal Notices
  • Privacy Notices
  • Security Information
  • Trust Center
© 2021 MongoDB, Inc.