Hibernating and Waking Up a Cluster (Pay-per-Use)
Scenario
If you do not need to use a cluster temporarily, you are advised to hibernate the cluster to save costs.
After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluster.
A hibernated cluster can be quickly woken up and used normally.
Notes and Constraints
Clusters billed on a yearly/monthly basis cannot be hibernated.
During cluster wakeup, the master node may fail to be started due to insufficient resources. As a result, the cluster fails to be woken up. Wait for a while and wake up the cluster again.
Hibernating a Cluster
- Log in to the CCE console. In the navigation pane, choose Clusters.
- Click
next to the cluster to be hibernated. Figure 1 Hibernating a cluster
- In the dialog box displayed, check the precautions and click Yes. Wait until the cluster is hibernated.
After a cluster is hibernated, the billing of master node resources will stop.
After a cluster is hibernated, resources, such as worker nodes (ECSs), bound EIPs, and bandwidth, are still billed based on their own billing modes. To shut down nodes, select Stop all nodes in the cluster in the dialog box or see Stopping a Node.
Figure 2 Prompt information
Waking Up a Cluster
- Log in to the CCE console. In the navigation pane, choose Clusters.
- Click
next to the cluster to be woken up. Figure 3 Waking up a cluster
- When the cluster status changes from Waking to Running, the cluster is woken up.
After the cluster is woken up, billing will be resumed for the resources on the master node.
Last Article: Renewing a Yearly/Monthly-Billed Cluster
Next Article: Changing the Billing Mode from Pay-per-Use to Yearly/Monthly
Did this article solve your problem?
Thank you for your score!Your feedback would help us improve the website.