Stopping and starting an MongoDB cluster
You can stop and restart a DB cluster as needed. There is no charge while your cluster is idle: you continue to pay only for the storage size and backups based on the pricing policy.
Alert
If a cluster uses local SSD storage (local-ssd
), its computing resources are not released when it's stopped. This means that you are charged in full even for a stopped cluster.
Stopping a cluster
- Go to the folder page
and select Managed Service for MongoDB. - Select the cluster you need in the list, click
, and select Stop. - Confirm that you want to stop the cluster and click Stop.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To stop a cluster, run the command:
yc managed-mongodb cluster stop <cluster_name_or_ID>
You can request the cluster ID or name with a list of clusters in the folder.
To stop a cluster, use the stop REST API method for the Cluster resource or the ClusterService/Stop gRPC API call and provide the cluster ID in the clusterId
request parameter.
You can get the cluster ID with a list of clusters in the folder.
Starting a cluster
You can restart STOPPED clusters.
- Go to the folder page
and select Managed Service for MongoDB. - Select the stopped cluster you need in the list, click
, and select Start. - Confirm that you want to start the cluster: click Start in the dialog box that opens.
If you do not have the Yandex Cloud command line interface yet, install and initialize it.
The folder specified in the CLI profile is used by default. You can specify a different folder using the --folder-name
or --folder-id
parameter.
To start a stopped cluster, run the command:
yc managed-mongodb cluster start <cluster_name_or_ID>
You can request the cluster ID and name with a list of clusters in the folder.
To start a cluster, use the start REST API method for the Cluster resource or the ClusterService/Start gRPC API call and provide the cluster ID in the clusterId
request parameter.
You can get the cluster ID with a list of clusters in the folder.