Navigation

Shut Down MongoDB Processes

Ops Manager supports shutting down individual mongod and mongos processes, as well as replica sets and sharded clusters. When you shut down a process, cluster, or replica set, Ops Manager continues to manage it.

After the process shuts down, you can restart or remove your processes.

No Alert Raised if User Shuts Down a MongoDB Process

If you shut down a MongoDB process, Ops Manager doesn’t tigger a host is down alert.

Shut Down One Entire Deployment

1

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

2

Shut down the deployment.

  1. Click ellipsis icon for the deployment that you want to shut down.
  2. Click Shutdown.
  3. Click Shutdown Process to 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.

Shut Down One Process in One Deployment

1

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

2

Select the deployment.

Click Modify for the deployment with the process that you want to shut down.

Ops Manager displays the Editing <myReplicaSet> page.

3

Shut down the deployment.

  1. Scroll to Member Configuration section of the page.
  2. Click ellipsis icon for the process that you want to shut down.
  3. Click Shutdown.
  4. Click Shutdown Process to confirm.
4

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.