ApsaraDB RDS:Restart an instance

Prerequisites

The instance is in the Running state.

Impacts

• A restart causes a connection interruption of approximately 30 seconds. Make sure that your business has an automatic reconnection mechanism. Stop business writes and make appropriate arrangements before the restart. Proceed with caution.

  Warning

  An RDS Basic Edition instance has only one database node and does not have a secondary node as a hot standby. The instance is unavailable for an extended period of time if the node unexpectedly fails, or when you perform tasks such as restarting the instance, changing specifications, or upgrading the version. If your business requires high database availability, do not use Basic Edition instances. Select another edition, such as High-availability Edition. Some Basic Edition instances support an upgrade to High-availability Edition.

• A restart releases the MySQL memory cache, including the buffer pool. It does not affect persisted data. The databases and tables on the instance remain intact after the restart.

• If the primary instance has read-only instances, restarting the primary instance does not restart the read-only instances. The replication relationship is automatically restored after the restart.

Restart an instance in the console

1. Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.

2. In the upper-right corner of the page, click Restart Instance.

3. In the confirmation dialog box, click OK.

   Warning

   After you click Restart Instance, the instance status changes to Restarting. This causes a connection interruption. Plan your business operations in advance.

FAQ

• Q: Apart from full connections or performance issues, in which other situations do I need to manually restart an instance?

  A: If temporary files cannot be deleted because the instance crashes while it is running, you can manually restart the instance. If other exceptions occur while the instance is running, you can also try a manual restart to recover the instance.

• Q: For a High-availability Edition instance, does restarting the primary instance cause a primary/secondary switchover?

  A: It depends on the actual situation. A primary/secondary switchover may occur. After the restart, the zones of the primary and secondary databases are swapped.

• Q: Do the endpoints and virtual IP address of the instance change after a restart?

  A: No, they remain unchanged.

• Q: Which factors affect the restart duration, and how do I reduce it?

  A: The restart duration is related to factors such as the number of databases and tables on the instance, the number of active connections, and the business traffic. To reduce the restart duration, avoid creating unnecessary databases or tables. Minimize active connections and business traffic before the restart. Reconnect your business after the restart is complete.

API reference