If a host fails, you can manually replace it. This option is available only if you selected Manual Host Replacement for the Host Troubleshooting Policy when you created your ApsaraDB for MyBase cluster.
Prerequisites
The ApsaraDB for MyBase cluster runs on the MySQL engine and uses hosts with local SSDs.
Background
When a host failure occurs, the system notifies you via SMS and the host's status changes to Ready for Replacement. You can view details about the failure in Scheduled Events. In the left-side navigation pane, click Pending Events. When the system detects a host failure, such as a damaged CPU, it generates an event. This event includes the Host ID/Host Name, Event Type, Event Action, Event Time, Event Source, and Event Cause. In the Actions column, you can select Execute Immediately or Postpone.
Impacts
Replacing a host has the following impacts:
-
The system stops allocating new instances to the host.
-
The system migrates all existing instances from the host.
-
All instances are migrated to a new, available host.
Procedure
-
Log on to the ApsaraDB for MyBase console.
-
In the upper-left corner of the page, select the region where your cluster resides.
-
In the left-side navigation pane, click Cluster List. Find the target cluster and click Details in the Actions column.
In the left-side navigation pane, click Hosts.
-
Find the target host, and then choose .
-
Select a replacement time and click OK.
Note-
switch within maintenance window: The system performs a primary/secondary switchover for any primary instances on the host during their specified maintenance windows. After all instances on the host become secondary, they are migrated to a new host.
-
switch immediately: The system immediately performs a primary/secondary switchover for any primary instances on the host. The resulting secondary instances are then migrated to a new host.
-