Shut Down MongoDB Processes
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
Cloud 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, Cloud Manager continues to manage it.
After the process shuts down, you can restart or remove your processes.
Note
No Alert Raised if User Shuts Down a MongoDB Process
If you shut down a MongoDB process, Cloud Manager doesn't trigger a
host is down (HOST_DOWN
) alert.
Shut Down One Entire Deployment
In MongoDB Cloud Manager, go to the Deployment page for your project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If the Deployment page is not already displayed, click Deployment in the sidebar.
The Deployment page displays.
Go to the Processes page.
Click the Processes tab for your deployment.
The Processes page displays.
Shut Down One Process in One Deployment
In MongoDB Cloud Manager, go to the Deployment page for your project.
If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
If the Deployment page is not already displayed, click Deployment in the sidebar.
The Deployment page displays.
Go to the Processes page.
Click the Processes tab for your deployment.
The Processes page displays.