Hibernating or Reactivating a Cluster

Scenario

If a cluster is not needed temporarily, hibernate it to reduce costs.

After a cluster is hibernated, resources such as workloads cannot be created or managed in the cluster.

Precautions

• During cluster wakeup, the master nodes may fail to start due to insufficient resources. This leads to a cluster wakeup failure. In this case, wait for a while and try again.
• After a cluster is woken up, it takes 3 to 5 minutes to initialize data. Deliver services after the cluster runs properly.

Hibernating a Cluster

1. Log in to the CCE console. In the navigation pane, choose Clusters.
2. Locate the cluster to be hibernated, click ... to view more operations on the cluster, and choose Hibernate.

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 Shut down 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 (ones with local disks attached, such as disk-intensive and ultra-high I/O ECSs).

Waking Up a Cluster

You can wake up a hibernated cluster as needed.

1. Log in to the CCE console. In the navigation pane, choose Clusters.
2. Click Wake Up in the row of the target cluster.
3. Check whether the cluster is woken up. 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.