If the resources you selected when you purchased your cluster are insufficient or excessive for your business requirements, you can scale the cluster. This topic describes how to scale a cluster.
Prerequisites
Your Alibaba Cloud account does not have unpaid renewal orders.
The cluster is in the Running state.
Background information
You can change the specifications of an AnalyticDB for MySQL cluster. For clusters in reserved mode, you can change the number of node groups and the storage space individually or at the same time. For clusters in elastic mode, you can change the computing resources and elastic I/O units individually or at the same time.
Time required for scaling
Scaling operations redistribute and migrate data. The time required for migration is proportional to the data volume. You can view the scaling progress on the Cluster List page in the console.
When you scale in a cluster from a larger to a smaller specification, data migration can take several hours or more. If your cluster contains a large amount of data, exercise caution when you scale in.
Impact of scaling
When you scale a cluster, you cannot execute the
SUBMIT JOBstatement to submit asynchronous jobs. If your business requires asynchronous jobs, perform scaling during appropriate periods.When the scaling process is about to end, transient connections may occur. We recommend that you scale your cluster during off-peak hours or make sure that your application is configured to automatically reconnect to your cluster.
When you change the disk level, note the following:
You cannot change other configurations when you change the disk level.
When you downgrade the disk level from PL1, PL2, or PL3 to PL0, you cannot submit asynchronous tasks using
SUBMIT JOB. If your business depends on this feature, schedule the downgrade for a suitable time window.When you downgrade the disk level from PL1, PL2, or PL3 to PL0, data is redistributed and migrated. The time required for migration is proportional to the data volume.
When you upgrade the disk level, data is not redistributed or migrated. Your business operations are not affected.
Billing
For more information, see Billing for specification changes.
Procedure
Elastic mode clusters
For elastic mode clusters, you can change the computing resources and elastic I/O units individually or at the same time. Follow these steps:
Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where your cluster is located. In the navigation pane on the left, click Cluster List and select a product series. Find the target cluster and click Scale Up or Scale Down in the Actions column.
On the Upgrade/Downgrade or Downgrade page, configure the parameters for the cluster.
Configuration
Description
Edition
Fixed to Data Warehouse Edition. You do not need to select it.
Mode
Fixed to Elastic Mode. You do not need to select it.
Series
Fixed to Cluster Edition (New). You do not need to select it.
Specifications
Fixed to E32. You do not need to select it.
Computing Resources
Select the Computing Resources for the cluster. Computing resources are used for data computation. Increasing computing resources can improve query speed. We recommend that the number of CPU cores for computing resources is greater than the number of CPU cores for elastic I/O units.
Specifications of 32 cores or more support resource groups, scheduled scaling, and hot and cold data separation.
Elastic I/O Unit Specifications
Select the Elastic I/O Unit Specifications for the cluster. The specification you select here is for a single node. A group of elastic I/O units contains 3 nodes.
An EIUs (EIU) is the basic unit for measuring the storage performance of a cluster in elastic mode. You can use it to scale storage resources independently. For more information, see Scale out elastic I/O units (EIUs).
After you scale out elastic I/O units, the amount of hot data locked by a single elastic I/O unit increases. For more information, see EIU-based storage performance metrics. To scale in, make sure that the amount of hot data is less than the amount of hot data that can be locked by the scaled-in specification. If the amount of hot data exceeds this limit, we recommend that you move some data to cold storage before you scale in.
Elastic I/O Units
Select the number of elastic I/O units.
NoteThis configuration is supported only for clusters that are in elastic mode and have Computing Resources of 32 Cores 128 GB or higher.
Disk Level
Select the disk level for the cluster. The capacity corresponding to each disk type is as follows:
PL0: 20 GiB to 65,536 GiB.
PL1: 20 GiB to 65,536 GiB.
PL2: 461 GiB to 65,536 GiB.
PL3: 1,261 GiB to 65,536 GiB.
ImportantWhen you change the disk level, you cannot change other configurations.
When you change the disk level, the amount of hot data must reach the minimum capacity of the selected disk level.
Changing the disk level affects the cost of hot storage space. You can calculate the cost of hot storage space using the formula:
Unit price of storage for the disk level × Amount of hot storage used × Duration. For the unit price of storage for different disk levels, see Data Warehouse Edition pricing.
For a Subscription cluster, read and select the Terms of Service, and click Buy Now. On the page that appears, confirm the order information and payment method, and then click . For a Pay-as-you-go cluster, read and select the Terms of Service, and then click Buy Now.
Reserved mode clusters
For reserved mode clusters, you can change the number of node groups and the storage space individually or at the same time. Follow these steps:
Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the region where your cluster is located. In the navigation pane on the left, click Cluster List and select a product series. Find the target cluster and click Scale Up or Scale Down in the Actions column.
On the Upgrade/Downgrade or Downgrade page, configure the parameters for the cluster.
Configuration
Description
Edition
Fixed to Data Warehouse Edition. You do not need to select it.
Series
Fixed to Cluster Edition. You do not need to select it.
Specifications
Select the product specifications.
Number Of Node Groups
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 of a single node group × Number of node groups.
Disk Level
Select the disk level for the cluster. The capacity corresponding to each disk type is as follows:
PL0: 20 GiB to 65,536 GiB.
PL1: 20 GiB to 65,536 GiB.
ImportantWhen you change the disk level, you cannot change other configurations.
When you change the disk level, the amount of hot data must reach the minimum capacity of the selected disk level.
Changing the disk level affects the cost of hot storage space. You can calculate the cost of hot storage space using the formula:
Unit price of storage for the disk level × Amount of hot storage used × Duration. For the unit price of storage for different disk levels, see Data Warehouse Edition pricing.
For a Subscription cluster, read and select the Terms of Service, and click Buy Now. On the page that appears, confirm the order information and payment method, and then click . For a Pay-as-you-go cluster, read and select the Terms of Service, and then click Buy Now.