This version of the documentation is archived and no longer supported. To learn how to upgrade your version of MongoDB Ops Manager, refer to the upgrade documentation.
You were redirected from a different version of the documentation. Click here to go back.

Restart Processes

You can restart a running sharded cluster, replica set, or standalone process directly from the Ops Manager console. Instead of restarting an entire deployment, you can also restart individual Ops Manager-managed MongoDB member processes of a deployment.


If Ops Manager Automation manages a mongos process and that process remains unreachable for 30 days, Ops Manager removes that process from the Deployment tab view. If you restart the mongos process, Ops Manager detects it again. To learn more, see the host is down alert.

To restart a process or deployment:


Restart the process or deployment.

  1. To restart a deployment, click the ellipsis icon [ ellipsis h icon ] next to the sharded cluster, replica set, or standalone process that you want to restart. To restart a single process of a deployment, click on the name of the deployment. Click the Actions dropdown next to the member process that you want to restart.
  2. Click Restart.
  3. Click Confirm.


If you are restarting a running deployment, after the next publish, Ops Manager restarts the sharded cluster, replica set, or standalone process. Deployments with multiple members should remain available as Ops Manager performs a rolling restart.


Click Review & Deploy to review your changes.

Ops Manager displays your proposed changes.

  1. If you are satisfied, click Confirm & Deploy.
  2. If you want to make further configuration changes, click Cancel. Click Modify for the cluster to make additional changes.