AnalyticDB for MySQL:Change a cluster from Data Warehouse Edition to Data Lakehouse Edition

Prerequisites

• Your Alibaba Cloud account does not have unpaid renewal orders.

• Your AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster meets the following conditions:

  • The cluster is in the Running state.

  • The cluster is in elastic mode for Cluster Edition.

  • The cluster has 32 cores and 128 GB memory or more.

  • The minor version of the cluster is 3.1.9.0 or later.

    Note

    For information about how to query the minor version of a cluster, see How do I query the version of an AnalyticDB for MySQL cluster? To update the minor version of a cluster, contact technical support.

Methods

You can use one of the following methods to change an AnalyticDB for MySQL cluster from Data Warehouse Edition (V3.0) to Data Lakehouse Edition (V3.0) based on your business requirements.

• Data Lakehouse Edition (V3.0) provides better data collection, storage, computing, and application capabilities. If you want to use more features of Data Lakehouse Edition (V3.0), you can directly change a cluster from Data Warehouse Edition (V3.0) to Data Lakehouse Edition (V3.0). After the edition change is complete, only the Data Lakehouse Edition (V3.0) cluster is retained. For more information about the procedure of this method, see the "Procedure" section of this topic.

• If you want to perform business testing such as stress testing in an environment that simulates real-world scenarios, you can clone a Data Warehouse Edition (V3.0) cluster to create a Data Lakehouse Edition (V3.0) cluster. After the edition change is complete, both the Data Warehouse Edition (V3.0) and Data Lakehouse Edition (V3.0) clusters are retained. For more information about the procedure of this method, see the "Procedure" section of the Clone a cluster topic.

Usage notes

• When you change the cluster edition, 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. During the switchover from the existing cluster to the new cluster, the existing cluster becomes read-only within 5 minutes to 10 minutes.

• During the edition change process, you are not allowed to execute the SUBMIT JOB statement to submit asynchronous jobs. If your business requires asynchronous jobs, change the edition of your cluster during appropriate periods.

• 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 Lakehouse Edition (V3.0) and Data Warehouse Edition (V3.0). If your business involves asynchronous jobs, perform mapping for asynchronous job status after the edition change is complete. For more information about the mappings of asynchronous job status, see the "Job status and mappings" section of the Asynchronously submit an import job topic.

Procedure

1. Submit a ticket to check whether your AnalyticDB for MySQL cluster meets the requirements to be changed from Data Warehouse Edition (V3.0) to Data Lakehouse Edition (V3.0).

   If your AnalyticDB for MySQL cluster meets the requirements, perform the following steps.

2. 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. On the Data Warehouse Edition (V3.0) tab, find the cluster for which you want to change the edition and choose More > Scale Down in the Actions column.

3. On the Downgrade page, configure the parameters that are described in the following table.

   Parameter	Description
   Version	The edition and version of the cluster. Select Data Lakehouse Edition (V3.0).
   Reserved Computing Resources	The reserved computing resources of the cluster. Select the same specifications as your AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster. For example, if your AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster has computing resources of 32 cores and 128 GB memory, set this parameter to 32 AnalyticDB compute units (ACUs). Important When you change a cluster from Data Warehouse Edition to Data Lakehouse Edition, you cannot change the computing resource specifications of the cluster. After the edition change is complete, you can upgrade or downgrade the cluster based on your business requirements.
   Default Allocation Behavior	Specifies whether to allocate all reserved computing resources to the user_default resource group. The loading process uses the reserved computing resources of the user_default resource group. If you want to load a built-in dataset, select Yes.
   Reserved Storage Resources	The reserved storage resources of the cluster.