Change a Data Warehouse Edition (V3.0) cluster from reserved mode to elastic mode - AnalyticDB

If you want to use features such as tiered storage of hot and cold data and scheduled scaling to reduce resource costs, or if you want to isolate computing resources between resource groups, you can change the cluster mode of an AnalyticDB for MySQL Data Warehouse Edition (V3.0) cluster from reserved mode to elastic mode.

Prerequisites

Your Alibaba Cloud account does not have unpaid renewal orders.
The minor version of the AnalyticDB for MySQL cluster is 3.1.3.9 or later. You can change the cluster mode of only AnalyticDB for MySQL clusters of V3.1.3.9 or later.
Note
For information about how to view the minor version of an AnalyticDB for MySQL cluster, see How do I view the minor version of a cluster? To update the minor version of a cluster, contact technical support.
The cluster is in the Running state.

Usage notes

When you change a cluster from reserved mode to elastic mode, you must apply for new cluster resources, perform full and incremental migration, and switch your business 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.
If you change the Enterprise SSD (ESSD) performance level, you cannot change other configurations.
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.
When a C32 cluster in reserved mode is changed to elastic mode, the specifications of a single node decrease to 8 cores. By default, BUILD jobs occupy 3 cores. In this case, the average CPU utilization increases. If the increased average CPU utilization does not affect your business, ignore this change. If your business is affected, upgrade your cluster or submit a ticket. For more information about BUILD jobs, see BUILD.

Billing rules

For information about the billing rules, see Billing of configuration changes.

Procedure

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 that you want to manage and click Scale Up or choose More > Scale Down in the Actions column.

On the Upgrade/Downgrade page or the Downgrade page, select Elastic Mode for the Mode parameter and configure the parameters that are described in the following table.

Parameter	Description
Version	The edition and version of the cluster. This parameter is automatically set to Data Warehouse Edition (V3.0). You do not need to configure this parameter.
Edition	Select Elastic Cluster.
Specifications	The specifications of the cluster. This parameter is automatically set to E32. You do not need to configure this parameter.
Computing Resources	The Computing Resources of the cluster. You can use computing resources to compute data. The increase in the computing resources can accelerate data queries. We recommend that you select more CPU cores for computing resources than those for storage resources.
EIU Specifications	The single-node specifications of an elastic I/O unit (EIU) for the cluster. Each EIU consists of three nodes. Elastic I/O resources are bundled into units and sold as EIUs. You can use EIUs to scale out storage resources for AnalyticDB for PostgreSQL clusters in elastic mode for Cluster Edition. 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 the "EIU-based storage performance metrics" section of the Scale out elastic I/O resources topic. If you want to scale in the elastic I/O resources, you must make sure that the amount of hot data in your cluster is less than the amount of hot data that can be supported by the elastic I/O resources after scale-in. If the preceding requirements cannot be met, we recommend that you migrate part of the data to cold storage before you scale in the elastic I/O resources.
EIUs	The number of EIUs. Note 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. ESSD performance levels provide the following capacities: PL0: 20 GiB to 65536 GiB. PL1: 20 GiB to 65536 GiB. Important When you change the ESSD performance level, you cannot change other configurations. When you change the ESSD performance level, the amount of hot data in your cluster must reach the minimum capacity that can be provided by the selected performance level. The hot storage fee varies based on the ESSD performance level. You can calculate the hot storage fee by using the following formula: `Unit storage price of an ESSD performance level × Hot storage size × Duration`. For information about the unit storage price of each ESSD performance level, see Pricing for Data Warehouse Edition.

For a subscription cluster, read and select the Terms of Service, and then click Buy Now. Confirm the order and the payment method, and then click Subscribe. For a pay-as-you-go cluster, read and select the Terms of Service, and then click Buy Now.