Restart an ApsaraDB RDS for MariaDB instance to recover from connection exhaustion, performance degradation, or other operational issues.
When to restart
| Situation | Description |
|---|---|
| Connection limit reached | Active connections hit the limit and new connections are rejected. |
| Performance degradation | The instance is unresponsive or performing poorly and other remediation steps have not resolved the issue. |
| Stuck temporary file | A temporary file cannot be deleted due to downtime. A restart clears it. |
| Other operational issues | General instability that a restart can resolve. |
How a restart works
Restarting stops and then starts the database service. During the restart, the instance status changes to Restarting and a connection interruption of approximately 30 seconds occurs. After the restart completes, the instance returns to Running.
If your instance runs RDS Basic Edition, no secondary instance is available as a hot standby. If the instance exits unexpectedly, restarts, undergoes a specification change, or has its database engine version upgraded, your database service becomes unavailable for an extended period. To maintain high availability, use RDS High-availability Edition instead. You can upgrade from RDS Basic Edition to RDS High-availability Edition. The upgrade is supported only when your RDS instance meets the specified requirements. For more information, see Upgrade the edition of an RDS instance from RDS Basic Edition to RDS High-availability Edition.
High-availability edition behavior
For instances running RDS High-availability Edition, a restart of the primary instance may trigger a primary/secondary switchover, which switches the zones of the primary and secondary instances.
Read-only instances
Read-only instances are not restarted when the primary instance is restarted. Data replication resumes automatically after the primary instance returns to Running.
Prerequisites
Before you begin, ensure that you have:
-
An ApsaraDB RDS for MariaDB instance in the Running state
Restart an instance
-
Go to the Instances page. In the top navigation bar, select the region where the instance resides. Find the instance and click its ID.
-
In the upper-right corner, click Restart Instance.
-
In the confirmation dialog, click OK.
The instance status changes to Restarting. After the restart completes, the status returns to Running. Endpoints and virtual IP addresses remain unchanged.
Reduce restart time
Restart time depends on the number of tables, databases, and active connections, and the current service traffic. To shorten the restart window:
-
Reduce active connections before restarting.
-
Reduce service traffic before restarting.
-
Keep only necessary tables and databases.
Configure your application to reconnect automatically. Stop writing data to the instance before restarting to avoid data loss.
FAQ
Do endpoints or virtual IP addresses change after a restart?
No. Endpoints and virtual IP addresses remain unchanged.
If I restart a primary instance running RDS High-availability Edition, does a primary/secondary switchover occur?
A switchover may occur. After the restart, the zones of the primary and secondary instances may be switched.
API reference
| Operation | Description |
|---|---|
| Restart an instance | Restarts an ApsaraDB RDS instance. |