|« PreviousNext »|
|Did this page help you? Yes | No | Tell us about it...|
In some cases, if you modify a DB instance, the DB parameter group associated with the instance, or a static DB parameter in a parameter group the instances uses, you must reboot the instance for the changes to take effect.
Rebooting a DB instance restarts the database engine service. A reboot also applies to the DB instance any modifications to the associated DB parameter group that were pending. Rebooting a DB instance results in a momentary outage of the instance, during which the DB instance status is set to rebooting. If the Amazon RDS instance is configured for MultiAZ, it is possible that the reboot will be conducted through a failover. An Amazon RDS event is created when the reboot is completed.
If your DB instance is deployed in multiple Availability Zones, you can force a failover from one AZ to the other during the reboot. You might force a failover to test the availability of your DB instance deployment or to restore operations to the original AZ after a failover occurs.
The time required to reboot is a function of the specific database engine's crash recovery process. To improve the reboot time, we recommend that you reduce database activities as much as possible during the reboot process to reduce rollback activity for in-transit transactions.
To reboot a DB instance
Sign in to the AWS Management Console and open the Amazon RDS console at https://console.aws.amazon.com/rds/.
In the navigation pane, click Instances.
Select the check box of the DB instance that you want to reboot.
Select Instance Actions and then select Reboot from the drop down menu.
To force a failover from one AZ to another, select the Reboot with failover? check box in the Reboot DB Instance dialog box.
Click Yes, Reboot. To cancel the reboot instead, click Cancel.