Help Center> GaussDB(for MySQL)> User Guide> Instance Lifecycle Management> Rebooting a DB Instance
Updated on 2024-05-21 GMT+08:00
View PDF

Rebooting a DB Instance

Scenarios

You may need to reboot a GaussDB(for MySQL) instance for maintenance reasons. For example, after changing some parameters, you must reboot the instance for the modifications to take effect.

Constraints

  • If the DB instance status is Abnormal, the reboot may fail.
  • To shorten the time required, you need to reduce database activities during the reboot to reduce a rollback of transit transactions.
  • Rebooting a DB instance will interrupt services. During this period, the instance status is Rebooting.
  • Rebooting DB instances will cause instance unavailability. To prevent traffic congestion during peak hours, reboot instances during off-peak hours.

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, locate the instance you want to reboot and choose More > Reboot in the Operation column.

    Alternatively, click the instance name to go to the Basic Information page. Click Reboot in the upper right corner of the page.

    The read replicas are also rebooted.

  5. 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.

  6. In the displayed dialog box, set Scheduled Time to Immediate or During maintenance window as needed.

    Figure 1 Rebooting an instance immediately

    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 DB instance during maintenance window

  7. View the task execution progress on the Task Center page. If its status is Available, it has been rebooted.

APIs