Rebooting a DB Instance

Scenarios

You may need to reboot a DB instance for maintenance reasons. For example, after you modify some parameters, a reboot is required for the modifications to take effect. You can reboot a DB instance on the console.

Constraints

• If the DB instance status is Abnormal, the reboot may fail.
• An instance cannot be rebooted if its storage is full.
• Rebooting a DB instance will cause service interruptions. During this period, the DB instance status is Rebooting.
• Rebooting DB instances will cause instance unavailability and clear cached memory. To prevent traffic congestion during peak hours, you are advised to reboot DB instances during off-peak hours.

Rebooting a DB Instance

1. Log in to the management console.
2. Click in the upper left corner and select a region.
3. Click in the upper left corner of the page and choose Databases > TaurusDB.
4. On the Instances page, locate the instance you want to reboot and choose More > Reboot in the Operation column.

   Alternatively, click the target DB instance on the Instances page to go to the Basic Information page. In the upper right corner, click Reboot.

   For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.

5. In the displayed dialog box, select the check box and click OK.
6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.