If you set the Host Troubleshooting Policy to Manual Host Replacement when creating your ApsaraDB for MyBase cluster, you can manually replace a failed host.
Prerequisites
An ApsaraDB for MyBase cluster must use the MySQL engine, and its hosts must use local SSDs.Background information
When a hardware failure occurs on a host, the system notifies you by text message, and the status of the host changes to Ready for Replacement. You can view details about this failure on the Scheduled Events page. On the Pending Events page, you can find more details in the event list, such as the event type and the cause of the failure (for example, a damaged CPU). In the Actions column, click Execute Now or Postpone to manage the host replacement event.
Impacts
- The system stops allocating new instances to the host.
- The system migrates all existing instances from the host.
- The system migrates the instances to a new, healthy host.
- During the host replacement, one or two transient service interruptions may occur. To minimize the impact on your business, we recommend selecting Switch Within Maintenance Window.
Procedure
- Log on to the ApsaraDB for MyBase console.
- In the upper-left corner of the page, select the target region.
- 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 choose .
- Select a replacement method and click OK.
Note
- Switch Within Maintenance Window: The system performs a primary/secondary instance switchover during the specified maintenance window. After all instances on the host become secondary instances, the system migrates them to a new host.
- Switch Immediately After Data Migration: The system immediately switches the primary instances on the host to secondary instances and then migrates the secondary instances to a new host.
该文章对您有帮助吗？