Rebooting a DB Instance

Scenarios

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

To reboot a DB instance, the following requirements must be met:

The status of the DB instance is Available.
No backup is being created or no read replica is being created.

You can reboot a DB instance only when its status is Available, Abnormal, or Storage full. Your database may be unavailable in some cases such as data is being backed up or some modifications are being made.
If the DB instance status is Abnormal, the reboot may fail.
Rebooting DB instances will reboot database services. Rebooting a DB instance will cause service interruption. During this period, the DB instance status is Rebooting.
Rebooting a DB instance will cause the instance unavailability and clear the cached memory in it. To prevent traffic congestion during peak hours, you are advised to reboot the DB instance during off-peak hours.

Procedure

Log in to the management console.
Click in the upper left corner and select a region and a project.
Click Service List. Under Database, click Relational Database Service. The RDS console is displayed.
On the Instance Management page, locate the target DB instance, or click in the front of a DB instance 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.

For primary/standby DB instances, if you reboot the primary DB instance, the standby DB instance is also rebooted automatically.
In the displayed dialog box, select a scheduled time, and click Yes.
Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.