Restart an ApsaraDB for ClickHouse cluster to recover from an outage or resolve a cluster issue.
Prerequisites
Before you begin, make sure that:
The cluster is in the Running state. The Restart Setting or Restart Instance button is unavailable if the cluster is not in the Running state
The cluster does not have a scheduled ZooKeeper primary node switchover
Potential impacts
Restarting a cluster may cause service interruptions. Schedule the restart during off-peak hours to minimize the impact on your business.
In most cases, the restart takes 1–2 minutes. The actual duration depends on:
Data volume — The more databases, tables, and data the cluster contains, the longer the restart takes
Tiered storage — If hot and cold-tiered storage is enabled, the cluster loads cold data during the restart, which extends the duration
Procedure
Restart a Community-compatible Edition cluster
The Community-compatible Edition supports two restart modes: restart all nodes at once, or restart selected nodes individually.
Log on to the ApsaraDB for ClickHouse console.
In the upper-left corner, select the region where the cluster is deployed.
On the Clusters page, click the Clusters of Community-compatible Edition tab, then click the ID of the cluster.
On the Cluster Information page, click Restart Setting in the upper-right corner.
In the Restart Setting dialog box, configure the following settings:
Select Node: Choose which nodes to restart.
Option Description All Restarts all nodes in the cluster. The cluster status changes to Restarting. Custom Restarts only the nodes you select, identified by node name or IP address. The cluster status changes to Node Restarting. Select Mode: Choose when to restart.
Option Description Restart Now Restarts the cluster immediately. Schedule Restart Restarts the cluster at the time you set in the Scheduled Time field.
Click OK.
The restart is complete when the cluster status returns to Running.
Restart an Enterprise Edition cluster
The Enterprise Edition restarts all nodes in the cluster.
Log on to the ApsaraDB for ClickHouse console.
In the upper-left corner, select the region where the cluster is deployed.
On the Clusters page, click the Clusters of Community-compatible Edition tab, then click the ID of the cluster.
On the Cluster Information page, click Restart Instance in the upper-right corner.
In the Restart Instance dialog box, click OK.
What's next
To modify or cancel a scheduled restart, see Cancel or modify a scheduled cluster restart.
API reference
To restart a Community-compatible Edition cluster via API, use RestartInstance.
To restart an Enterprise Edition cluster via API, use RestartDBInstance.