Restart a host in an ApsaraDB MyBase dedicated cluster to recover from performance degradation or other host-level issues.
When to restart a host
Restart a host when the host itself—not an individual instance—is experiencing problems that cannot be resolved through instance-level operations. Common triggers include:
Sustained performance degradation on the host (high CPU, memory pressure, or I/O bottlenecks that persist across instances)
Unresponsive host behavior that is not caused by a specific instance
How it works
Restarting a host triggers a primary/secondary instance switchover for all instances running on that host:
The primary instance on the host stops serving traffic.
A secondary instance takes over as the new primary.
During the switchover, one or two transient connections may occur.
The total restart time depends on how long the primary/secondary instance switchover takes.
- The MyBase Redis engine does not support host restarts.
Prerequisites
Before you begin, make sure you have:
Access to the ApsaraDB for MyBase console
The required permissions to manage hosts in your dedicated cluster
Restart a host
Log on to the ApsaraDB for MyBase console.
In the upper-left corner of the page, select a region.
In the left-side navigation pane, click Hosts.
Find the host that you want to restart and choose More > Restart Host in the Actions column.
In the Restart Host dialog box, select Restart Immediately and click OK.