Question: How to restart a MongoDB cluster?


Restarting a MongoDB cluster involves restarting the mongod and mongos processes on the respective nodes. This process may slightly differ based on your deployment (replica set or sharded cluster) and whether you are using MongoDB as a service (like Atlas) or managing it yourself. Here’s a general approach for a self-managed cluster:

For a Replica Set

  1. Connect to each replica set member: You need to access each member of the replica set either via SSH or through your cloud provider's management console.

  2. Stop the mongod process:

    • On Linux, use the command sudo systemctl stop mongod if MongoDB was installed using a package manager and managed with systemd.
    • Alternatively, if you're using an init system, you might use sudo service mongod stop.
  3. Start the mongod process:

    • Use sudo systemctl start mongod for systems using systemd.
    • Or, sudo service mongod start for systems using init.

Repeat these steps for each member of the replica set, one at a time, to ensure high availability.

For a Sharded Cluster

A sharded cluster includes mongos routers, config servers, and shard servers (each being a replica set). Restart components in the following order:

  1. Config Servers: Restart all the config servers (one at a time if there are multiple) using the same method described above for replica sets.

  2. Shard Servers: For each shard (which is a replica set), restart all members using the procedure outlined for replica sets.

  3. Mongos Routers: Finally, restart all mongos processes. If these are running as services:

    • Use sudo systemctl restart mongos for systemd.
    • Or, sudo service mongos restart for init systems.


  • Configuration File: If you need to make changes to the MongoDB configuration (stored in mongod.conf or mongos.conf), do so before restarting the services.
  • Data Integrity: Ensure that there are no ongoing write operations that could be interrupted by the restart. It's a good practice to step down the primary in a replica set gracefully using the rs.stepDown() command in the mongo shell before stopping the process.
  • Monitoring: After restarting, monitor the logs and the performance metrics of your MongoDB cluster to ensure that all components are functioning correctly and there are no unforeseen issues.

Automation Tools

For larger deployments, consider using automation tools like Ops Manager or Cloud Manager (for MongoDB Enterprise) or orchestration tools like Kubernetes or Docker Swarm for managing the lifecycle of your MongoDB instances efficiently.

Was this content helpful?

Start building today

Dragonfly is fully compatible with the Redis ecosystem and requires no code changes to implement.