Rebooting a GaussDB Node

Scenarios

If the status of a GaussDB instance node is abnormal, you can reboot the node to restore the node status. You can also reboot a node when it is in the Available state. A node is not available when it is being rebooted.

Precautions

• You can reboot a node when the DB instance is in the following state or performing the following operations:
  • Backup and restoration failed
  • Changing the billing mode from pay-per-use to yearly/monthly
  • DR in progress for the primary instance in a streaming DR task
  • Caching logs for the primary instance in a streaming DR task
  • DR simulation in progress for the DR instance in a streaming DR task
  • DR in progress for the DR instance in a streaming DR task
  • DR instance promoted to primary in a streaming DR task
• Rebooting nodes will clear the cached memory in them. To prevent traffic congestion during peak hours, you are advised to reboot nodes during off-peak hours.
• Only nodes of centralized instances can be rebooted.
• A primary/standby switchover will be triggered if a primary node is rebooted.

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 and choose Databases > GaussDB.
4. Click the target instance name to go to the Basic Information page.
5. In the Node List area, click Reboot in the Operation column of a node. Confirm information about the node to be restarted, enter reboot, and click OK.

   The node status becomes Rebooting node.

6. Refresh the instance basic information and check the reboot result. If the node status is Available, the reboot is successful.