Help Center/ GaussDB(for MySQL)/ User Guide/ Instance Lifecycle Management/ Rebooting a DB Instance
Updated on 2023-10-18 GMT+08:00
View PDF

Rebooting a DB Instance

Scenarios

You may need to reboot an 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 an 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 Database > 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. In the displayed dialog box, click Yes.
  6. View the task execution progress on the Task Center page. If its status is Available, it has been rebooted.