Rebooting DB Instances or Read Replicas

Graceful: If the DB instance is running properly and there are no uncommitted transactions, you can select this option.
Forceful: If the graceful reboot request cannot be delivered, you can reboot the instance forcibly. Uncommitted transactions will be interrupted.

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.

You can reboot a single DB instance or multiple DB instances at a time.

Constraints

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.

Normal Reboot

Log in to the management console.
Click in the upper left corner of the page and choose Databases > Relational Database Service.
On the Instances 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 instance name on the Instances page to go to the Overview 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, set required parameters and click OK.

**Table 1** Parameter description
Parameter	Description
Reboot Mode	Graceful: If the DB instance is running properly and there are no uncommitted transactions, you can select this option. Forceful: If the graceful reboot request cannot be delivered, you can reboot the instance forcibly. Uncommitted transactions will be interrupted.
Object to Be Rebooted	Database instance: Only the DB instance is rebooted. The underlying VM is not rebooted.