AnalyticDB:Change a single-zone to a multi-zone deployment

Prerequisites

• The cluster is either Enterprise Edition or Data Lakehouse Edition.

• The cloud disk performance level of the cluster is PL0 or PL1.

Billing

After the configuration change, your hot data storage is billed at the price of Zone-redundant ESSDs, which is 1.5 times the price of PL1 disks. If you also modify the specifications or number of reserved resource nodes on the Change Configuration page, the cost for reserved resources also changes. For pricing details, see Pricing of Enterprise Edition and Basic Edition and Pricing of Data Lakehouse Edition.

Duration

During the configuration change, the system remounts Zone-redundant ESSDs. The time required for this process is proportional to your data volume. After you start the change, you can monitor its progress on the Clusters page or in the Task Center.

Impacts

During the configuration change, the system rebuilds the cluster nodes. This may cause minor jitter in query and write operations. After the nodes are rebuilt, the system switches over to the new nodes. The switchover process takes approximately 5 to 10 minutes, during which read and write operations are unavailable.

We recommend performing this operation during off-peak hours. Alternatively, you can run the following statement to set a time window for the cluster switchover. The following example sets the time window to 23:00–23:30:

SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;

Procedure

1. Log on to the AnalyticDB for MySQL console. In the upper-left corner, select your cluster's region. In the left-side navigation pane, click Clusters.

2. On the Clusters page, find the target cluster and click Scale Out in the Actions column.

3. On the Upgrade/Downgrade page, configure the following parameters:

   Parameter	Description
   Scaling Type	Fixed to Same Version Change.
   Version	The edition of your cluster, which is either Enterprise Edition or Data Lakehouse Edition.
   Deployment Mode	Select Multi-zone Deployment.
   Primary Availability Zone	Select the primary zone for the cluster.
   vSwitch in Primary Zone	If you have already created a VPC that meets your network requirements, select that VPC. For example, if you have an ECS instance in a suitable VPC, select that VPC. If you do not have a suitable VPC, you can use the default VPC and vSwitch. For more information, see Default VPCs and vSwitches. If the default VPC and vSwitch do not meet your requirements, you can create your own. For instructions, see Create and manage a VPC.
   Secondary Zone	Select a secondary zone for the cluster. If the primary zone fails, the cluster automatically fails over to the secondary zone. During the failover, read and write operations might be unavailable or time out.
   vSwitch in Secondary Zone	If you have already created a VPC that meets your network requirements, select that VPC. For example, if you have an ECS instance in a suitable VPC, select that VPC. If you do not have a suitable VPC, you can use the default VPC and vSwitch. For more information, see Default VPCs and vSwitches. If the default VPC and vSwitch do not meet your requirements, you can create your own. For instructions, see Create and manage a VPC.
   Single-node Specifications of Reserved Resources	Defaults to the current specifications. You can change them if they do not meet your business requirements.
   Reserved Resource Nodes	Defaults to the current number of nodes. You can change this number in increments of 3 if it does not meet your business requirements.
   Disk Level	Fixed to Regional ESSD.

4. For a Subscription cluster, accept the terms of service and click Buy Now, confirm the order details and payment method, and then click Buy Now. For a Pay-as-you-go cluster, accept the terms of service and then click Buy Now.

Related topics

cross-zone disaster recovery: An overview of cross-zone disaster recovery.