Multi-zone clusters provide higher disaster recovery capabilities than single-zone clusters, and can withstand data center-level failures. In the event of a failure, the system performs an automatic failover to ensure service continuity. This topic guides you through changing a cluster's deployment mode from single-zone to multi-zone.
Prerequisites
The cluster product series is Enterprise Edition or Data Lakehouse Edition.
The disk performance level of the cluster is PL0 or PL1.
Billing
After the configuration change, the hot data storage will be billed at the price of regional Enterprise SSD (ESSD), which is 1.5 times the price of PL1 disks. If you also modify the reserved resource node specifications or the number of reserved resource nodes on the configuration change page, the reserved resource fees will also change. For billing details, see Enterprise Edition and Basic Edition pricing and Data Lakehouse Edition pricing.
Duration
During the configuration change, the system needs to remount the regional ESSD. The duration required is proportional to the data volume. After you initiate the change, you can monitor its progress on the Cluster List page or Task Hub page in the console.
Impact
During the configuration change process, nodes will be rebuilt. You may experience slight jitter in query and write operations during this period. After the rebuild is complete, the system will switch between old nodes and new ones. This switchover takes approximately 5 to 10 minutes, during which read and write operations cannot be performed.
You are recommended to perform this change during off-peak hours, or execute the following statement to specify a time window for cluster switchover (in this example, the time window is 23:00 to 23:30):
SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;Procedure
Log on to the AnalyticDB for MySQL console, select the region where your cluster is located in the upper-left corner. In the left-side navigation pane, click Clusters.
On the Clusters page, click Scale Down in the Actions column of the target cluster.
On the Change Configuration page, configure the parameters.
Parameter
Description
Change Type
Fixed as Same Version Change.
Version
The product series of the cluster. Valid values: Enterprise Edition or Data Lakehouse Edition.
Deployment Mode
Select Multi-zone Deployment.
Primary Zone
Select the primary zone where the cluster is located.
Primary Zone VSwitch
If you have created a virtual private cloud (VPC) that meets your business requirements, you can select the VPC. For example, if you have created an Elastic Compute Service (ECS) instance in a VPC that meets your business requirements, select the VPC.
If you have not created a VPC that meets your business requirements, you can use the default VPC and vSwitch. For more information, see Default VPCs and default vSwitches.
If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPCs and vSwitches. For more information, see Create and manage a VPC.
Secondary Zone
Select the secondary zone where the cluster is located. If the primary zone fails, the cluster workloads are automatically switched to the secondary zone. During the switchover, the cluster may be unavailable for read and write operations or experience read and write timeouts.
Secondary Zone VSwitch
If you have created a virtual private cloud (VPC) that meets your business requirements, you can select the VPC. For example, if you have created an Elastic Compute Service (ECS) instance in a VPC that meets your business requirements, select the VPC.
If you have not created a VPC that meets your business requirements, you can use the default VPC and vSwitch. For more information, see Default VPCs and default vSwitches.
If the default VPC and vSwitch cannot meet your business requirements, you can create your own VPCs and vSwitches. For more information, see Create and manage a VPC.
Reserved Resource Node Specifications
Default to the current reserved resource node specifications of the cluster.
If the selected reserved resource node specifications do not meet your business requirements, you can manually change the specifications.
Number Of Reserved Resource Nodes
Default to the current number of reserved resource nodes of the cluster. The step size is 3.
If the selected reserved resource node specifications do not meet your business requirements, you can manually change the number of nodes.
Disk Performance Level
Fixed as Zone-redundant ESSD.
For a Subscription cluster, read and select the Service Agreement, click Buy Now, confirm the unpaid order information and payment method, and then click Buy Now. For a Pay-as-you-go cluster, read and select the Service Agreement, and then click Buy Now.
References
For more information, see Cross-zone disaster recovery.