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

The newly launched Enterprise Edition and Basic Edition of AnalyticDB for MySQL integrate the benefits of Data Warehouse Edition in reserved mode, Data Warehouse Edition in elastic mode, and Data Lakehouse Edition. Enterprise Edition and Basic Edition use a storage-compute coupled architecture for reserved resources to ensure expected query performance. In scenarios that involve periodic or sudden changes in business workloads, you can increase or decrease computing resources based on your business requirements. This topic describes how to change a cluster from Data Lakehouse Edition or Data Warehouse Edition to Enterprise Edition or Basic Edition.

Prerequisites

Your Alibaba Cloud account does not have unpaid renewal orders.
An AnalyticDB for MySQL cluster is in the Running state.
The minor version of the AnalyticDB for MySQL cluster is 3.1.10.6 or later.
Note
To view and update the minor version of an AnalyticDB for MySQL cluster, log on to the AnalyticDB for MySQL console and go to the Configuration Information section of the Cluster Information page.
The Data Lakehouse Edition cluster meets the following requirements:
- The cluster does not have a resource group whose configurations are being changed or a resource group that is being created, modified, started, or stopped.
- The cluster does not have an Interactive Resource Group scaling plan or EIU scaling plan.

Amount of time required to change configurations

Data Lakehouse Edition

If you modify the configurations of reserved resource nodes when you change the edition of a cluster, scaling occurs on the cluster. The amount of time required to change configurations varies based on the following conditions:

When you scale a cluster, data in the cluster is migrated for redistribution. The amount of time that is required to migrate data is proportional to the amount of data.
When you downgrade cluster specifications, data migration may require up to dozens of hours to complete. Proceed with caution especially if the cluster contains a large amount of data.

Data Warehouse Edition

When you change the edition of a cluster, you must apply for new cluster resources, perform full and incremental data migration, and then switch your workloads from the existing cluster to the new cluster. The amount of time that is required for the entire process varies based on the cluster specifications and data volume.

Impacts of configuration changes

Data Lakehouse Edition

After you change a cluster from Data Lakehouse Edition to Enterprise Edition, you cannot restore the cluster edition to Data Lakehouse Edition.
When you change the edition of a cluster, you cannot perform control operations or execute the INSERT OVERWRITE statement on the Data Lakehouse Edition cluster. Other read and write operations are not affected.
When you change the edition of a cluster, transient connections or query errors may occur. We recommend that you change the edition of the cluster during off-peak hours or make sure that your application is configured to automatically reconnect to the cluster.
If you modify the configurations of reserved resource nodes when you change the edition of a cluster, scaling occurs on the cluster. Take note of the following items:
- When you scale a cluster, you cannot execute the SUBMIT JOB statement to submit asynchronous jobs. If your business requires asynchronous jobs, perform scaling during off-peak hours.
- When you scale down a cluster, make sure that each reserved resource node does not contain an excessive number of shards. Select an appropriate number of reserved resource nodes to ensure that the amount of reserved resources remains similar to the amount of original reserved storage resources. For more information, see error messages.

Data Warehouse Edition

After you change a cluster from Data Warehouse Edition to Enterprise Edition or Basic Edition, you cannot restore the cluster edition to Data Warehouse Edition.
You cannot change a Data Warehouse Edition cluster whose specifications are S8 or S16 to Enterprise Edition or Basic Edition.
During the switchover from the existing cluster to the new cluster, the existing cluster becomes read-only for a period of 5 to 10 minutes.
After you connect to the existing cluster, execute the following statement to specify the time window for the switchover. In this example, the specified time window for the switchover is 23:00 to 23:30.
```
SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;
```
For information about how to connect to an AnalyticDB for MySQL cluster, see Connect to an AnalyticDB for MySQL cluster.
If you continuously execute SUBMIT JOB statements to submit asynchronous jobs or ongoing asynchronous jobs exist during the edition change process, the switchover process is blocked.
When the edition change process is about to end, transient connections may occur. We recommend that you change the edition of your cluster during off-peak hours or make sure that your application is configured to automatically reconnect to your cluster.
The asynchronous job status is different between Data Warehouse Edition, Enterprise Edition, and Basic Edition. If your business involves asynchronous jobs, perform mapping for asynchronous job statuses after the edition change is complete. For information about the mappings of asynchronous job statuses, see the "Job statuses and mappings" section of the Asynchronously submit an import job topic.
The underlying backup logic of Data Warehouse Edition is different from the underlying backup logic of Enterprise Edition and Basic Edition. After you change a cluster from Data Warehouse Edition to Enterprise Edition or Basic Edition, the backup sets generated by the Data Warehouse Edition cluster immediately become invalid and cannot be used for cluster cloning. However, the backup cycle configuration remains unchanged.
Data Warehouse Edition supports different billing methods and features from Enterprise Edition and Basic Edition. For more information, see Editions and Pricing.
For example, after you change a cluster from Data Warehouse Edition to Enterprise Edition, the cluster allows you to create job resource groups and XUANWU_V2 tables that are billed based on the pay-as-you-go billing method. In this case, you are charged for them based on the actual usage.

Procedure

(Optional) Submit a ticket to check whether your AnalyticDB for MySQL cluster meets the edition change requirements.
If your AnalyticDB for MySQL cluster meets the edition change requirements, perform the following steps:
Log on to the AnalyticDB for MySQL console. In the upper-left corner of the console, select a region. In the left-side navigation pane, click Clusters.
Go to the configuration change page.
- If you estimate that the cluster configurations are downgraded after the edition change, find the cluster that you want to manage and choose More > Scale Down in the Actions column.
- If you estimate that the cluster configurations are upgraded after the edition change, find the cluster that you want to manage and click Scale Up in the Actions column.
Note
When you perform cluster scaling, AnalyticDB for MySQL compares the costs of the original and new clusters. If the new cluster costs more than the original cluster, the Upgrade/Downgrade page that appears after you click Scale Up needs to be used. If the new cluster costs less than the original cluster, the Downgrade page that appears after you choose More > Scale Down needs to be used. You can estimate the costs of the original and new clusters in advance based on documentation. For more information, see Pricing.

On the Upgrade/Downgrade or Downgrade page, configure the parameters that are described in the following table.

Parameter	Description
Configuration Change Type	The configuration change type of the cluster. Select Cross-edition Configuration Change .
Edition	The edition to which you want to change the cluster. Select Enterprise Edition (Multi-replica) or Basic Edition (Single-replica). For information about Enterprise Edition and Basic Edition, see Editions. Important You can change a Data Lakehouse Edition cluster only to Enterprise Edition.
Single-node Specifications of Reserved Resources	When you scale up or down a cluster, AnalyticDB for MySQL automatically recommends single-node resource specifications of reserved resources that align with the performance of the source cluster. If the recommended specifications do not meet your business requirements or far exceed the specifications of resources used for business operations, you can also manually adjust the single-node resource specifications of reserved resources. Recommended rules: When you scale up a cluster, AnalyticDB for MySQL recommends a configuration where the CPU and memory allocated for computing or storage after the scale-up are not lower than the specifications of the source cluster. When you scale down a cluster, AnalyticDB for MySQL recommends a configuration that provides the best possible performance without surpassing the original cost of the source cluster. Note For information about the specification mappings between Data Warehouse Edition, Data Lakehouse Edition, and Enterprise Edition, see the "Specification mappings between Data Warehouse Edition, Data Lakehouse Edition, and Enterprise Edition" section of the Create a cluster topic. If the amount of reserved resources is 0 ACUs, you can use only external tables. If you want to create AnalyticDB for MySQL internal tables, make sure that the amount of reserved resources is greater than 0 ACUs. If you select 0 ACUs of reserved resources when you create a cluster, you can purchase reserved resources later by scaling up the cluster. For more information, see Scale an Enterprise Edition or Basic Edition cluster.
Reserved Resource Nodes	When you scale up or down a cluster, AnalyticDB for MySQL automatically recommends the number of reserved resource nodes that aligns with the performance of the source cluster. If the recommended number of nodes does not meet your business requirements or far exceeds the number of resources nodes used for business operations, you can manually adjust the number of reserved resources nodes. Recommended rules: When you scale up a cluster, AnalyticDB for MySQL recommends a configuration where the CPU and memory allocated for computing or storage after the scale-up are not lower than the specifications of the source cluster. When you scale down a cluster, AnalyticDB for MySQL recommends a configuration that provides the best possible performance without surpassing the original cost of the source cluster. Note The number of reserved resource nodes in an Enterprise Edition cluster is 3, and the number of reserved resource nodes in a Basic Edition cluster is 1.
ESSD Performance Level	The Enterprise SSD (ESSD) performance level of the cluster. Valid values: PL1 PL2 PL3

Note

If the reserved resources that you select for changing the cluster edition do not meet your business requirements, you can scale the cluster after the edition change is complete.

Read and select the Terms of Service and click Buy Now.
Note
After the edition change is complete, the status of the cluster changes to Running and you can use the cluster as expected.