Navigation
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.
This version of the manual is no longer supported.

Restart One MongoDB Deployment

If an Ops Manager-managed MongoDB process isn’t currently running, restart it from the Ops Manager console.

To restart a running standalone process, replica set, or sharded cluster, see Restart a Running Deployment.

Note

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 one deployment:

1

Click Deployment, then the Processes tab, then the Topology view.

2

Restart the process.

  1. Click ellipsis icon for the deployment that you want to shut down.
  2. Click Restart.
  3. Click Confirm.
3

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.

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.