Restart an ApsaraDB for MyBase instance to resolve connection limit exhaustion or performance issues. Restarting causes about 30 seconds of service interruption.
When to restart
Restart an instance in the following situations:
Connection limit reached: The instance has hit its maximum connection count and cannot accept new connections.
Performance degradation: The instance is unresponsive or experiencing abnormal performance.
Before you begin
Ensure that you have:
An ApsaraDB for MyBase instance running MySQL, SQL Server, or PostgreSQL. For setup instructions, see:
The instance is in the Running state
Your application is configured to automatically reconnect to the instance after a restart
Restarting interrupts your service for about 30 seconds. Restart during off-peak hours to minimize user impact.
Restart an instance
Log on to the ApsaraDB for MyBase console.
In the upper-left corner, select a region.
In the left-side navigation pane, click Instances. Click the database engine of the instance. Find the instance you want to restart, and click Details in the Actions column.
Use one of the following methods to restart the instance:
Method A: In the upper-right corner, click Restart Instance.
Method B (MySQL Master-replica Edition only): In the left-side navigation pane, click Service Availability. Hover over the instance and click Restart.
NoteThis method is available only for ApsaraDB MyBase for MySQL Master-replica Edition instances.
In the confirmation dialog, click OK.
ImportantAfter the restart, the instance state changes to Restarted and your service may experience transient connections.
Enter the verification code received on your mobile phone.
What's next
To restart an instance programmatically, see Restart an ApsaraDB for RDS instance.