Rebooting a Node

Scenarios

You can reboot a node of your DB instance on the management console to reconnect the database.

Constraints

• The nodes in the Abnormal state can be rebooted.

• The time required for rebooting a node depends on the crash recovery process of the DB engine. To shorten the time required, reduce database activities during the reboot to reduce rollback of transit transactions.
  

  • Rebooting a node will cause service interruption. During this period, the node status is Rebooting node.
  • The node is not available when it is being rebooted. To prevent traffic congestion during peak hours, you are advised to reboot the node during off-peak hours.
  • If a parameter of your DB instance is modified, you need to first reboot the DB instance for the modification to take effect, and then reboot a node of the DB instance.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click in the upper left corner of the page, choose Databases > GaussDB(for MySQL).
4. On the Instances page, click the instance name to go to the Basic Information page.
5. In the Node List area, locate a node that you want to reboot and choose Reboot in the Operation column.
6. If you have enabled operation protection, click Start Verification in the displayed dialog box. On the displayed page, click Send Code, enter the obtained verification code, and click Verify to close the page.

   For details about how to enable operation protection, see Identity and Access Management User Guide.

7. In the displayed dialog box, set Scheduled Time to Immediate or During maintenance window.
   Figure 1 Rebooting a node
   
   1. To reboot the instance immediately, set Scheduled Time to Immediate and click Yes.
   2. To reboot the instance during the maintenance window, set Scheduled Time to During maintenance window and click Yes. You can also change the maintenance window by clicking Change.

      Changing the maintenance window will not affect the timing that has already been scheduled.

      A reboot task configured during a current maintenance window will not be executed until the next maintenance window.

      Figure 2 Rebooting a node during maintenance window
      

8. View the task execution progress on the Task Center page. If the node status is Available, the reboot is complete.

APIs

• Rebooting a Node
• Rebooting a DB Instance