Change a Data Warehouse edition cluster from Reserved Mode to Elastic Mode - AnalyticDB

Elastic mode enables tiered storage of hot and cold data, scheduled scaling, and computing resource isolation between resource groups for AnalyticDB for MySQL Data Warehouse Edition (V3.0) clusters. This topic describes how to change a cluster from reserved mode to elastic mode.

How it works

Changing from reserved mode to elastic mode involves three stages:

Resource provisioning -- The system applies for new cluster resources for elastic mode.
Data migration -- Full and incremental data migration runs from the existing cluster to the new cluster.
Business switchover -- Traffic switches from the existing cluster to the new cluster.

The total time varies based on your cluster specifications and data volume.

Important

During the switchover stage, the existing cluster becomes read-only for 5 to 10 minutes. Plan accordingly for production workloads.

Prerequisites

Before you begin, make sure that:

Your Alibaba Cloud account has no unpaid renewal orders
The cluster minor version is 3.1.3.9 or later
The cluster is in the Running state

Note

To check your cluster's minor version, see How do I view the minor version of a cluster?. To update the minor version, contact technical support.

Switchover window

During the switchover from the existing cluster to the new cluster, the existing cluster becomes read-only for 5 to 10 minutes. To control when this happens, connect to the existing cluster and run the following SQL statement to specify a switchover time window. The following example sets the window to 23:00 through 23:30:

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

For connection instructions, see Connect to an AnalyticDB for MySQL cluster.

Constraints

Constraint	Details
ESSD performance level change	You cannot change other configurations at the same time.
C32 cluster CPU impact	When a C32 cluster changes from reserved mode to elastic mode, single-node specifications decrease to 8 cores. By default, BUILD jobs occupy 3 cores, which increases the average CPU utilization. If this affects your workloads, upgrade your cluster or Submit a ticket. For more information about BUILD jobs, see BUILD.

Billing

For billing details, see Billing of configuration changes.

Procedure

Log on to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left-side navigation pane, click Clusters. On the Data Warehouse Edition (V3.0) tab, find the target cluster. Click Scale Up in the Actions column, or choose More > Scale Down.

On the Upgrade/Downgrade page or the Downgrade page, set the Mode parameter to Elastic Mode and configure the following parameters.

Important

When changing the ESSD performance level:

You cannot change other configurations at the same time.
The hot data in your cluster must reach the minimum capacity for the selected performance level.
The hot storage fee is calculated as: Unit storage price of the ESSD performance level x Hot storage size x Duration. For unit storage prices, see Pricing for Data Warehouse Edition.

Parameter	Description
Version	Automatically set to Data Warehouse Edition (V3.0). No configuration required.
Edition	Select Elastic Cluster.
Specifications	Automatically set to E32. No configuration required.
Computing Resources	The computing resources for the cluster. Computing resources are used for data computation. Increasing the computing resources accelerates data queries. Select more CPU cores for computing resources than for storage resources.
EIU Specifications	The single-node specifications of an elastic I/O unit (EIU). Each EIU consists of three nodes. EIUs bundle elastic I/O resources for AnalyticDB for MySQL clusters in elastic mode. For more information, see Scale out elastic I/O resources. After you scale out elastic I/O resources, the amount of hot data that is locked by each EIU increases. For more information, see EIU-based storage performance metrics. To scale in elastic I/O resources, make sure the hot data in your cluster is less than the capacity supported after scale-in. If the preceding requirements cannot be met, we recommend that you migrate some data to cold storage before you scale in.
EIUs	The number of EIUs. This parameter takes effect only when the Mode parameter is set to Elastic Mode and the Computing Resources parameter is set to 32 cores and 128 GB or more.
ESSD Performance Level	The ESSD performance level of the cluster. Available levels and capacities: PL0: 20 GiB to 65,536 GiB. PL1: 20 GiB to 65,536 GiB.

Complete the purchase:
- Subscription cluster: Read and select the Terms of Service, and then click Buy Now. Confirm the order and the payment method, and then click .
- Pay-as-you-go cluster: Read and select the Terms of Service, and then click Buy Now.