Help Center> Relational Database Service> User Guide> Working with RDS for MySQL> Instance Management> Rebooting a DB Instance
View PDF

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. You can reboot a single DB instance or multiple DB instances at a time.

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 a DB instance will cause service interruption. During the reboot process, 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.
  • A reboot task configured during the current maintenance window will not be executed until the next maintenance window.

Rebooting a DB Instance

  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.

    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, select a scheduled time, and click Yes.

    You can select During maintenance window for Scheduled Time and click Change. On the displayed Basic Information page, change the maintenance window.

    Figure 1 Rebooting a DB instance as scheduled

  6. If you have enabled the operation protection function, click Send Code in the displayed Identify Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication is required to improve the security of your account and cloud product. For details about how to enable operation protection, see the Identity and Access Management User Guide.

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

Rebooting DB Instances in Batches

  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, select one or more DB instances to be rebooted (a maximum of 50 instances can be selected) and click Reboot above the DB instance list.
  5. In the displayed dialog box, click Yes.
  6. If you have enabled the operation protection function, click Send Code in the displayed Identify Verification dialog box and enter the obtained verification code. Then, click OK.

    Two-factor authentication is required to improve the security of your account and cloud product. For details about how to enable operation protection, see the Identity and Access Management User Guide.

  7. Refresh the DB instance list and view the status of the DB instance. If its status is Available, it has rebooted successfully.
Parent topic: Instance Management