This topic describes how to manually restart an ApsaraDB RDS instance. If the number of connections to your RDS instance exceeds the specified threshold or if your RDS instance encounters performance issues, you can manually restart the instance.
- During the restart process, your RDS instance encounters a transient connection of about 30 seconds. Before you restart your RDS instance, we recommend that you make suitable arrangements for your workloads. Proceed with caution.
Note If you are using the RDS Basic Edition, your RDS instance does not have a secondary RDS instance as a hot standby. In this case, if your RDS instance exits unexpectedly, your database service becomes unavailable. If you change the specifications or upgrade the database engine version of your RDS instance, your database service also becomes unavailable. The unavailability may last for a long period of time. If you require high service availability, we recommend that you do not select the RDS Basic Edition. For example, you can select the RDS High-availability Edition. Alternatively, you can upgrade your RDS instance from the RDS Basic Edition to the RDS High-availability Edition. The upgrade is supported only when your RDS instance meets the specified requirements. For more information, see Upgrade an RDS instance to the High-availability Edition.
- After your RDS instance is restarted, ApsaraDB RDS updates your RDS instance to the latest minor engine version. This applies if your RDS instance uses local SSDs. For more information, see Updates the minor engine version of an ApsaraDB RDS for PostgreSQL instance.
- Visit the RDS instance list, select a region above, and click the target instance ID.
- In the upper-right corner of the Basic Information page, click Restart Instance.
- In the message that appears, click OK.
|Restart an ApsaraDB for RDS instance||Restarts an ApsaraDB RDS instance.|