Rebooting DB Instances

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 one or more DB instances at a time on the console.

Constraints

• If the DB instance status is Abnormal, the reboot may fail.
• Rebooting a DB instance will reboot the DB engine service, causing service interruptions. During this period, the 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.
• After a primary/standby DB instance is rebooted, it takes about one minute to establish the replication relationship. During this period, some operations, such as changing the instance class, cannot be performed.

Procedure

1. In the instance list, select one or more DB instances (maximum: 50) to be rebooted and click Reboot above the instance list.
2. In the displayed dialog box, enter YES and click OK.
   Figure 1 Rebooting a DB instance
   

3. View the instance status. If the status is Available, the instance has been rebooted successfully.