Rebooting a Node of a Standard HTAP Instance

Scenarios

You may need to reboot a node of an HTAP instance for maintenance reasons.

Constraints

• You can reboot a node only when it is available or abnormal. When some operations such as creating a task, changing specifications, scaling up storage, and upgrading a minor version, are being performed on a node, the node cannot be rebooted.

• It takes about 1 to 2 minutes to reboot a node of an HTAP instance. During the reboot, the instance is unavailable. Rebooting a node will clear its cache. To prevent traffic congestion during peak hours, you are advised to reboot the node during off-peak hours.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and project.
3. Click in the upper left corner of the page, choose Databases > GaussDB(for MySQL).
4. On the Instances page, locate a GaussDB(for MySQL) instance and click its name to access the Basic Information page.
5. In the navigation pane, choose HTAP Analysis. Locate an HTAP instance and click its name to access the Basic Information page.
6. Locate an HTAP node and click Reboot in the Operation column.
7. In the displayed dialog box, click OK to reboot the node. It takes about 1 to 2 minutes.