Suspend an ApsaraDB for ClickHouse Enterprise Edition cluster when it's idle to stop compute capacity unit (CCU) consumption and eliminate computing fees. Start the cluster again when you need it.
How it works
When a cluster has no read or write operations and no merge tasks running, you can suspend it. The cluster enters the Suspended state, CCUs drop to zero, and computing fees stop accruing.
When read or write requests are sent to your cluster, or merge tasks are created in your cluster, you can start the cluster. The cluster returns to the Running state and computing fees resume.
When not to suspend
Avoid suspending clusters that serve latency-sensitive or frequently accessed workloads:
-
Any connection attempt to a Suspended cluster returns a timeout error.
-
Starting a cluster takes about 5 minutes. During startup, expect elevated request latency.
-
While the cluster is in Suspending or Starting state, the cluster can only be accessed. Management operations such as scaling and restart are not supported.
Prerequisites
Before you begin, ensure that you have:
-
An ApsaraDB for ClickHouse Enterprise Edition cluster. To create one, see Create an ApsaraDB for ClickHouse cluster.
Suspend a cluster
-
Log on to the ApsaraDB for ClickHouse console.
-
In the top navigation bar, select the region where the cluster resides.
-
On the Clusters page, click the Enterprise Edition Clusters tab.
-
In the Actions column of the target cluster, click the
icon, and then click Suspend. -
In the Suspend Cluster dialog, click OK.
The cluster status changes from Suspending to Suspended in about 5 minutes.
Start a cluster
-
Log on to the ApsaraDB for ClickHouse console.
-
In the top navigation bar, select the region where the cluster resides.
-
On the Clusters page, click the Enterprise Edition Clusters tab.
-
In the Actions column of the target cluster, click the
icon, and then click Start. -
In the Start Cluster dialog, click OK.
The cluster status changes from Starting to Running in about 5 minutes.