Change a Data Warehouse or Data Lakehouse cluster to Enterprise or Basic Edition - AnalyticDB

AnalyticDB for MySQL has introduced Enterprise Edition and Basic Edition. These editions consolidate the strengths of Data Warehouse Edition (Reserved Mode), Data Warehouse Edition (Elastic Mode), and Data Lakehouse Edition. Reserved resources use a storage-compute integrated architecture to ensure consistent query performance for regular workloads. If your workload changes periodically or spikes, you can elastically scale compute resources up or down. If you want to change a Data Lakehouse Edition or Data Warehouse Edition cluster to Enterprise Edition or Basic Edition, this document describes how to perform this change.

Prerequisites

Your Alibaba Cloud account has no unpaid renewal orders.
The AnalyticDB for MySQL cluster is in the Running state.
The minor version of the AnalyticDB for MySQL cluster must be 3.1.10.6 or later.

Note
To view and update the minor version, go to the Configuration Information section on the Cluster Information page in the AnalyticDB for MySQL console.
In addition to the preceding prerequisites, Data Lakehouse Edition clusters must meet the following conditions:
- The cluster has no resource groups in the Creating, Modifying, Upgrading/Downgrading, Starting, or Stopping state.
- The cluster has no active scaling plans for an Interactive Resource Group or an EIU.

Duration

Data Lakehouse Edition

If you adjust the reserved resource nodes when changing the edition, the cluster is scaled. The duration is as follows:

The scaling operation migrates and redistributes data. The migration time is proportional to the amount of data.
When scaling down a cluster with a large data volume, migration can take several to dozens of hours. Proceed with caution.

Data Warehouse Edition

The configuration change involves provisioning new cluster resources, performing a full data migration and an incremental data migration, and switching over from the old cluster to the new one. The duration of this process depends on the cluster specifications and data volume.

Impacts

Data Lakehouse Edition

Once a Data Lakehouse Edition cluster is changed to Enterprise Edition, it can no longer be restored to its original state (that is, Data Lakehouse Edition).
During the configuration change, you cannot perform control operations or run INSERT OVERWRITE statements on the Data Lakehouse Edition cluster. Other data read and write operations are not affected.
During the configuration change, transient connection interruptions may occur and some queries may fail. Perform this operation during off-peak hours or ensure that your application has an automatic reconnection mechanism.
If you adjust the reserved resource nodes during the change, the cluster is scaled. Note the following:
- During scaling, you cannot submit asynchronous jobs by using the SUBMIT JOB statement. If your business depends on this feature, perform the scaling operation during a suitable time window.
- When you scale down, do not drastically reduce the number of reserved resource nodes, as this can lead to an excessive number of shards per node. For more information, see the error message.

Data Warehouse Edition

Once a Data Warehouse Edition cluster is changed to Enterprise Edition or Basic Edition, it cannot be changed back to its original state (Data Warehouse Edition).
Clusters with S8 and S16 specifications cannot be changed to Enterprise Edition or Basic Edition.
During the switchover, the original cluster enters a read-only state for 5 to 10 minutes.
You can connect to the original cluster and run the following statement to specify a switchover time window. The following example sets the window to 23:00–23:30.
```
SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;
```
For information about how to connect to a cluster, see Connect to a cluster.
During a configuration change, if the cluster continuously submits asynchronous jobs by using the SUBMIT JOB statement, or if there are incomplete asynchronous jobs, the switchover process is blocked.
When the configuration change is about to complete, transient connection interruptions may occur. We recommend that you perform the configuration change during off-peak hours or ensure that your application has an automatic reconnection mechanism.
The Data Warehouse Edition uses different asynchronous job statuses than the Enterprise Edition and Basic Edition. If your business uses asynchronous job statuses, you must manually map them after a configuration change. For more information about asynchronous job status mapping, see Job Status and Mapping Relationships.
The Data Warehouse Edition has a different underlying backup logic from the Enterprise Edition and Basic Edition. After a configuration change to the Enterprise Edition or Basic Edition, backup sets created on the Data Warehouse Edition are immediately invalidated and cannot be used to clone new instances. However, the backup schedule of the original instance is retained.
The billing methods and supported features of Data Warehouse Edition differ from those of Enterprise Edition and Basic Edition. For more information, see editions and Pricing.

For example, after you change a Data Warehouse Edition cluster to Enterprise Edition, you can create elastic resource groups (job-oriented resource groups) and XUANWU_V2 tables. These features are billed on a pay-as-you-go basis and will incur additional charges.

Procedure

(Optional) Submit a ticket to have technical support assess the configuration change.

If the assessment confirms that your cluster meets the requirements, proceed to the next step.
Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where your cluster is located. In the left-side navigation pane, click Clusters.
Go to the configuration change page.
- To scale down the specifications, find the target cluster and choose More > Scale In.
- To scale up the specifications, find the target cluster and click Scale Out in the Actions column.
Note
AnalyticDB for MySQL determines whether the change is a scale-up or scale-down based on cost. If the new specifications cost more, you are directed to the Scale Out page. If they cost less, you are directed to the Scale In page. You can estimate the cluster price by using the pricing calculator or by referring to the relevant pricing documentation. For more information, see Pricing.

On the Scale Up or Scale Down page, configure the cluster parameters.

Parameter	Description
Scaling Type	Select Cross-edition Configuration Change.
Version	Select Enterprise Edition (Multi-replica) or Basic Edition (Single-replica). For more information about Enterprise Edition and Basic Edition, see editions. Important Data Lakehouse Edition clusters can only be changed to Enterprise Edition.
Single-node specifications of reserved resources	AnalyticDB for MySQL recommends target specifications that match the performance of your source cluster. You can adjust this recommendation to meet your business needs. The recommendation rules are as follows: When you scale up: AnalyticDB for MySQL recommends specifications with at least the same amount of CPU and memory for compute or storage as the source cluster. When scaling down, AnalyticDB for MySQL recommends the optimal specifications at a price no higher than the purchase price of the source cluster. Note For information about the mapping between the specifications of Data Warehouse Edition, Data Lakehouse Edition, and Enterprise Edition, see Mapping between the specifications of Enterprise Edition, Data Lakehouse Edition, and Data Warehouse Edition. If the reserved resources are 0 ACU, you can use only external tables. To create internal tables in AnalyticDB for MySQL, the reserved resources must be greater than 0 ACU. If you select 0 ACU for reserved resources during the configuration change, you can purchase reserved resources by scaling up the cluster after the configuration change is complete. For more information, see Scale an Enterprise Edition or Basic Edition cluster.
Reserved resource nodes	AnalyticDB for MySQL recommends a target number of nodes that matches the performance of your source cluster. You can adjust this recommendation to meet your business needs. The recommendation rules are as follows: When you scale up: AnalyticDB for MySQL recommends specifications with at least the same amount of CPU and memory for compute or storage as the source cluster. When scaling down, AnalyticDB for MySQL recommends the optimal specifications at a price no higher than the purchase price of the source cluster. Note The number of reserved resource nodes for an Enterprise Edition cluster can be changed in increments of 3. For a Basic Edition cluster, the increment is 1.
ESSD performance level	Select the ESSD performance level for the cluster. The following performance levels are supported: PL1 PL2 PL3

Note

If the reserved resources do not meet your business requirements after the configuration change, you can scale the cluster.

Read and select the terms of service, and then click Buy Now.

Note
After the configuration change is complete, you can use the cluster when its status changes to Running.