Rebooting DB Instances or Read Replicas

Scenarios

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

Constraints

• If the DB instance status is Abnormal, the reboot may fail.
• Rebooting DB instances will cause service interruptions. During the reboot process, 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.

Procedure

1. Log in to the management console.
2. Click in the upper left corner and select a region and a project.
3. Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
4. On the Instance Management page, locate the target DB instance, or click and then locate the target read replica. Choose More > Reboot in the Operation column.

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

   You can also select the target DB instance on the Instance Management page and choose More > Reboot above the DB instance list.

   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, click Yes.
   • Immediate: RDS reboots the instance immediately.
   • During maintenance window: RDS will reboot the instance during the maintenance window you configured.

6. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.