Scale a Data Warehouse Edition cluster and change the cluster mode - AnalyticDB

If the resources you selected when purchasing a cluster cannot meet the normal operation of your business, or far exceed the resources used by your business, you can refer to this topic to complete the scaling operation.

Prerequisites

Your Alibaba Cloud account has no unpaid renewal orders.
The cluster is in the Running state.

Background information

AnalyticDB for MySQL clusters support changing cluster specifications. You can individually or simultaneously change the number of node groups and storage space in reserved mode, and computing resources and elastic I/O resources in elastic mode.

Scaling duration

The scaling operation redistributes and migrates data. The migration duration is proportional to the data volume. You can view the scaling progress on the Clusters page in the console.
When you scale down a cluster from a larger specification to a smaller one, data migration usually takes several hours or even tens of hours. Proceed with caution when the data volume is large.

Scaling impact

During scaling, SUBMIT JOB is disabled for submitting asynchronous tasks. If your business depends on this feature, schedule the scaling operation during off-peak hours.
Near the end of the scaling operation, brief connection interruptions may occur. We recommend that you perform scaling during off-peak hours or ensure that your application has an automatic reconnection mechanism.
When you change the cloud disk level, note the following:
- You cannot change other configurations when you change the cloud disk level.
- When you downgrade the cloud disk level from PL1, PL2, or PL3 to PL0, SUBMIT JOB is disabled for submitting asynchronous tasks. If your business depends on this feature, schedule the scaling operation during off-peak hours.
- When you downgrade the cloud disk level from PL1, PL2, or PL3 to PL0, data is redistributed and migrated. The migration duration is proportional to the data volume.
- When you upgrade the cloud disk level, data is not redistributed or migrated. Normal business operations are not affected.

Billing

For more information, see Change the billing method of a cluster.

Procedure

Elastic mode cluster

Elastic mode clusters support individually or simultaneously changing computing resources and elastic I/O resources. Perform the following steps:

Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where the cluster is deployed. In the left-side navigation pane, click Clusters. Select a product series and click Scale Out or Scale In on the right side of the target cluster.

On the Change Configuration or Downgrade page, configure the cluster settings.

Configuration	Description
Version	Fixed to Data Warehouse Edition. No selection required.
Mode	Fixed to Elastic Mode. No selection required.
Series	Fixed to Cluster Edition (New). No selection required.
Specification	Fixed to E32. No selection required.
Computing Resource	Select the computing resource for the cluster. Computing resources are used for data computing. Increasing computing resources can improve data query speed. We recommend that the CPU cores of computing resources are more than those of elastic I/O resources. Specifications of 32 cores and above support resource groups, time-based elasticity, and hot/cold data separation.
Elastic I/O Resource Specification	Select the elastic I/O resource specification for the cluster. The specification selected here is for a single node. Each group of elastic I/O resources contains 3 nodes. Elastic I/O Resource (Elastic IO Unit, EIU for short) is the base unit for measuring cluster storage performance in elastic mode. You can use EIUs to independently scale out storage resources. For more information, see Scale out elastic I/O resources (EIU). After elastic I/O resources are scaled out, the amount of hot data locked by each elastic I/O resource increases. For more information, see Storage performance metrics based on EIUs. If you need to scale back, make sure that the hot data volume is less than the maximum hot data volume that can be locked by the scaled-in specification. If the hot data volume exceeds the maximum, we recommend that you move some data to cold storage before you perform the scale-in operation.
Elastic I/O Resource	Select the number of elastic I/O resource groups. Note This configuration is supported only when the mode is Elastic Mode and the Computing Resource is 32 cores 128 GB or a higher specification.
Cloud Disk Level	Select the cloud disk level for the cluster. The following list describes the capacity ranges for different cloud disk types: PL0: 20 to 65536 GiB. PL1: 20 to 65536 GiB. PL2: 461 to 65536 GiB. PL3: 1261 to 65536 GiB. Important You cannot change other configurations when you change the cloud disk level. When you change the cloud disk level, the hot data volume must meet the minimum capacity of the selected cloud disk level. Changing the cloud disk level affects the cost of hot storage space. You can calculate the cost of hot storage space by using the following formula: `Unit price of storage space for the cloud disk level × Hot storage space usage × Duration`. For the unit prices of storage space for different cloud disk levels, see Data Warehouse Edition pricing.

For a Subscription cluster, read and select the service agreement, click Buy Now, confirm the unpaid order information and payment method, and then click . For a Pay-as-you-go cluster, read and select the service agreement, and then click Buy Now.

Reserved mode cluster

Reserved mode clusters support individually or simultaneously changing the number of node groups and storage space. Perform the following steps:

Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where the cluster is deployed. In the left-side navigation pane, click Clusters. Select a product series and click Scale Out or Scale In on the right side of the target cluster.

On the Change Configuration or Downgrade page, configure the cluster settings.

Configuration	Description
Version	Fixed to Data Warehouse Edition. No selection required.
Series	Fixed to Cluster Edition. No selection required.
Specification	Select a product specification.
Node Group Count	Select the number of node groups. Each node group contains three nodes (replicas) by default.
Storage Space	Select the storage space for a single node group. If you purchase multiple node groups, the total storage space = Storage space per node group × Number of node groups.
Cloud Disk Level	Select the cloud disk level for the cluster. The following list describes the capacity ranges for different cloud disk types: PL0: 20 to 65536 GiB. PL1: 20 to 65536 GiB. Important You cannot change other configurations when you change the cloud disk level. When you change the cloud disk level, the hot data volume must meet the minimum capacity of the selected cloud disk level. Changing the cloud disk level affects the cost of hot storage space. You can calculate the cost of hot storage space by using the following formula: `Unit price of storage space for the cloud disk level × Hot storage space usage × Duration`. For the unit prices of storage space for different cloud disk levels, see Data Warehouse Edition pricing.

For a Subscription cluster, read and select the service agreement, click Buy Now, confirm the unpaid order information and payment method, and then click . For a Pay-as-you-go cluster, read and select the service agreement, and then click Buy Now.