Stopping and starting an Redis 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.
Stopping a cluster
You can stop the cluster if you're not going to use the DBMS you launched for a while.
- In the management console
, go to the folder containing the cluster you need to stop. - Select Managed Service for Redis.
- In the line with the cluster, 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-redis cluster stop <cluster_name_or_ID>
You can request the cluster ID and 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.
To find out the cluster ID, get a list of clusters in the folder.
Starting a cluster
You can restart STOPPED clusters.
- In the management console
, go to the folder containing the cluster you need to start. - Select Managed Service for Redis.
- In the line with the cluster, 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 cluster, run the command:
yc managed-redis 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.
To find out the cluster ID, get a list of clusters in the folder.