Stop, start & restart database
Two lifecycle operations are available on a MongoDB Enterprise cluster: restart and delete. Which one you can run depends on the cluster's current status.
The operations
- Restart — stops and starts the cluster. Used to apply configuration changes or clear transient problems. Status shows Restarting, returning to Running when complete.
- Delete — removes the cluster and all its data, and releases the associated resources.
Delete is irreversible. The cluster and its data are gone, and a backup taken before deletion is the only way back. Confirm you have a usable restore point before deleting anything you might need.
What each status allows
| Status | Meaning | Available actions |
|---|---|---|
| Processing | The cluster is provisioning. | Delete |
| Running | Operating normally. | Restart, Delete |
| Warning | Degraded performance or stability. | Delete |
| Failed | Hit an unknown error. Delete it if no longer needed, or contact FPT Support. | Delete |
Restart is available only from Running. A cluster in Warning cannot be restarted out of that state from the console — that case needs FPT Support.
Perform an operation
- Open the database cluster list.
- In the Action column for the target cluster, select the ⋯ (More actions) icon.
- Choose the action. A confirmation dialog appears — confirm explicitly to proceed.
The operation typically takes 5–7 minutes. Other operations on the cluster are disabled until it completes.
Restarting drops every open connection. Applications reconnect on their own only if their driver is configured to retry — otherwise plan the restart alongside an application restart.
Next steps
- Resource management — reducing compute triggers an automatic restart
- Maintenance Window to control when platform maintenance restarts the cluster
- Backup & Restore overview — take a backup before deleting anything you might still need