Hibernating and Waking Up a Cluster

Scenario

If you do not need to use a cluster temporarily, you are advised to hibernate the cluster.

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.

Constraints

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

1. Log in to the CCE console. In the navigation pane, choose Clusters.
2. Click next to the cluster to be hibernated.
3. 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. 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.

   Most nodes are no longer billed after they are stopped, excluding certain types of ECSs with a local disk attached (such as a disk-intensive or ultra-high I/O ECS)..

Waking Up a Cluster

1. Log in to the CCE console. In the navigation pane, choose Clusters.
2. Click next to the cluster to be woken up.
3. When the cluster status changes from Waking up to Running, the cluster is woken up. It takes about 3 to 5 minutes to wake up the cluster.
   

   After the cluster is woken up, the cluster management fee continues to be billed.