ApsaraDB for ClickHouse allows you to restart a cluster. If an ApsaraDB for ClickHouse cluster becomes unavailable or needs to be restarted to resolve issues, you can restart the cluster. This topic describes how to restart a cluster in the ApsaraDB for ClickHouse console.
Prerequisites
The cluster is in the Running state.
The cluster does not have a scheduled Zookeeper primary node switchover.
Impacts
In most cases, the restart process takes between 1 and 2 minutes, and the exact duration varies based on the following factors:
Number of databases and tables and data volume: The more databases, tables, and data stored in a cluster, the longer it takes to start the cluster.
Hot and cold-tiered storage: If the tiered storage feature is enabled for the cluster, the cluster must load cold data during the restart. This can extend the restart duration.
If you restart a cluster, service interruptions may occur. We recommend that you restart the cluster during off-peak hours.
Procedure
Restart a Community-compatible Edition cluster
Log on to the ApsaraDB for ClickHouse console.
In the upper-left corner, select the region where the cluster that you want to manage is deployed.
On the Clusters page, click the Clusters Of Community-compatible Edition tab, and click the ID of the cluster that you want to manage.
On the Cluster Details page, click Restart Setting in the upper-right corner.
In the Restart Setting dialog box, configure Node Selection and Mode Selection based on your business requirements.
Node Selection:
All Nodes: All nodes in the cluster will be restarted.
Partial Nodes: Only the selected nodes will be restarted. You can select the nodes that you want to restart based on node names and node IP addresses.
Mode Selection:
Schedule Restart: In the Scheduled Time field, set the time when you want to restart the cluster. The cluster will be restarted at the scheduled time.
Restart Now: The cluster will be restarted immediately.
Click OK.
The cluster status during restart varies depending on your node selection:
All Nodes: The cluster status is Restarting.
Partial Nodes: The cluster status is Node Restarting.
After the cluster status changes to Running, the restart is complete.
Restart an Enterprise Edition cluster
Log on to the ApsaraDB for ClickHouse console.
In the upper-left corner, select the region where the cluster that you want to manage is deployed.
On the Clusters page, click the Enterprise Edition Clusters tab, and click the ID of the cluster that you want to manage.
On the Cluster Details page, click Restart Instance in the upper-right corner.
In the Restart Instance dialog box, click OK.
Follow the on-screen instructions to complete the verification, and click OK.
NoteDuring the restart, the cluster status changes to Restarting. After the cluster status changes to Running, the restart is complete.
References
To modify or cancel a scheduled restart, see Cancel or modify a scheduled cluster restart.
Related API operations
You can call the RestartDBInstance operation to restart an Enterprise Edition cluster. For more information, see RestartDBInstance.
You can call the RestartInstance operation to restart a Community-compatible Edition cluster. For more information, see RestartInstance.