Resource scaling plans automate scheduled scale-out and scale-in of cluster resources. Use them when your workloads follow predictable peak and off-peak patterns, or when computing or storage resources are insufficient during specific time windows. Unlike manual scaling, resource scaling plans require no data migration and don't interrupt reads or writes.
Create resource scaling plans from the AnalyticDB for MySQL console or by calling API operations.
Prerequisites
Before you begin, ensure that you have:
An AnalyticDB for MySQL cluster. To check your cluster edition, log in to the AnalyticDB for MySQL console, go to the Clusters page, click the cluster ID, and find the Cluster Attributes section.
For Enterprise Edition, Basic Edition, and Data Lakehouse Edition clusters: no additional requirements.
For Data Warehouse Edition clusters, all of the following:
The cluster is in Elastic mode
The cluster has at least 32 cores and 128 GB of memory
Minor version 3.1.3.2 or later (required for Default Proportional Scaling for Computing Resources and EIUs plans)
Minor version 3.1.6.1 or later, purchased at new prices (required for Scaling for Computing Resources and Scaling for EIUs plans)
To view or update the minor version, go to the Configuration Information section of the Cluster Information page in the AnalyticDB for MySQL console.
Usage notes
During scaling, you cannot run the
SUBMIT JOBstatement to submit asynchronous jobs. Schedule scaling plans during periods when asynchronous jobs are not required.When scaling completes, brief transient connections may occur. Schedule scaling during off-peak hours and configure your application to reconnect automatically.
For Basic Edition and Data Warehouse Edition (Standalone in Elastic mode) clusters: the cluster is unavailable during scaling — reads, writes, and control operations are all blocked. Schedule scaling during off-peak hours and configure your application to reconnect automatically.
Billing
Resources used during scaling plan execution are billed on a pay-as-you-go basis. For details, see the billing documentation for your edition:
Scaling plan types
The available scaling plan types depend on your cluster edition.
Enterprise Edition and Basic Edition
These editions use a compute-storage coupled architecture. Scaling plans scale out the reserved resources of the cluster.
Data Lakehouse Edition
| Scaling type | What it scales | Use when |
|---|---|---|
| Interactive Resource Group | Computing resources only, to the desired specifications | Computing resources are insufficient |
| Default Proportional Scaling for EIUs | Storage resources (elastic I/O units), proportionally, when an Interactive Resource Group plan fires | Resource needs fluctuate predictably across peak and off-peak periods |
| EIU | Storage resources (elastic I/O units) only, to the desired specifications | Storage resources are insufficient — for example, when importing large volumes of data daily for BI report analysis |
Data Warehouse Edition
| Scaling type | What it scales | Use when |
|---|---|---|
| Scaling for Computing Resources | Computing resources, added on top of original specifications | Computing resources are insufficient |
| Default Proportional Scaling for Computing Resources and EIUs | Computing resources (added to original specs) and elastic I/O resources (scaled proportionally) | Resource needs fluctuate predictably across peak and off-peak periods |
| Scaling for EIUs | Elastic I/O resources, to the desired specifications | Storage resources are insufficient — for example, when importing large volumes of data daily for BI report analysis |
Create a resource scaling plan
To implement a full scale-out and scale-in cycle, you need two separate plans: one to scale out resources at peak time and another to scale them back at off-peak time. For example, to scale out at 06:00 and scale in at 22:00 every day, create two plans with different scaling times and desired specifications. See How do I schedule scale-out and scale-in?
Enterprise Edition and Basic Edition
Important
You cannot change cluster configuration while resource scaling plans are active. To change the cluster configuration, first disable all scaling plans, make the change, then re-enable them. See Manage a resource scaling plan.
Procedure
Timing constraints for Scaling Time:
To run a plan on the day you create or modify it, the Scaling Time must be at least 1 hour from the current time.
The interval between multiple scaling plans must be at least 1 hour.
Log in to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left navigation pane, click Clusters. On the Enterprise Edition or Basic Edition tab, find the cluster and click its ID.
In the left navigation pane, choose Cluster Management > Resource Management.
On the Resource Management page, click the Scaling Plans tab, then the CloudMonitor consoleResource Scaling Plans tab, and click Create Plan in the upper-right corner.
In the Create Resource Scaling Plan panel, configure the following parameters.
Parameter Description Plan Name A name for the scaling plan. Desired Specifications per Reserved Resource Set The target specifications for each reserved resource set. Cannot be lower than the single-node specifications of the cluster's reserved resources. For Enterprise Edition, each set contains 3 nodes — for example, 48 ACUs (8 ACUs × 6 Nodes) equals 2 sets, so setting each set to 36 ACUs yields 72 ACUs total. For Basic Edition, each set contains 1 node — for example, 8 ACUs (8 ACUs × 1 Node) equals 1 set, so setting it to 24 ACUs yields 24 ACUs total. Scaling Cycle The days on which the plan runs. Scaling Time (Cluster-specific) The time when reserved resources are automatically scaled to the desired specifications. Enabled Whether to enable the plan immediately. Enabled by default. To disable later, find the plan on the Resource Scaling Plans tab and click Disable in the Actions column. Effective Date The date from which the plan starts running. Expiration Date The date after which the plan stops running. The plan expires after 23:59:59 on this date. Reserved resources are not automatically restored to their original specifications when a plan expires — create a separate plan with the original specifications to restore them. Click OK.
The plan appears on the Resource Scaling Plans tab. You can view Plan Name, Desired Specifications, Status, and Next Effective Time (Cluster-specific).
Data Lakehouse Edition
Important
Constraints:
You cannot change cluster configuration while scaling plans are active. Disable all plans before changing the cluster configuration, then re-enable them.
You cannot enable the multi-cluster feature and resource scaling plans (Interactive Resource Group or Default Proportional Scaling for EIUs) for the same interactive resource group simultaneously.
You cannot enable an EIU plan and a Default Proportional Scaling for EIUs plan at the same time.
Only one Default Proportional Scaling for EIUs plan can be active at a time.
A Default Proportional Scaling for EIUs plan only takes effect when an Interactive Resource Group plan is also enabled.
If reserved storage is 0 ACUs (AnalyticDB Compute Units), only Interactive Resource Group plans can be created.
Procedure
Log in to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left navigation pane, click Clusters, find the cluster, and click its ID.
In the left navigation pane, choose Cluster Management > Resource Management.
On the Resource Management page, click the Scaling Plans tab, then the Resource Scaling Plans tab, and click Create Plan in the upper-right corner.
In the Create Resource Scaling Plan panel: Interactive Resource Group plan: Timing constraints for Scaling Time: EIU plan: Timing constraints for Scaling Time:
Configure Plan Name, Effective Date, and Expiration Date.
Parameter Description Plan Name A name for the scaling plan. Effective Date The date from which the plan starts running. Expiration Date The date after which the plan stops running. The plan expires after 23:59:59 on this date. Select a Scaling Type and configure its parameters.
The interval from the current time must be at least 1 hour (for same-day execution).
The interval between multiple EIU plans must be at least 1 hour.
No active Default Proportional Scaling for EIUs plan: the interval from the current time must be at least 10 minutes (for same-day execution), and at least 10 minutes between multiple Interactive Resource Group plans.
An active Default Proportional Scaling for EIUs plan exists: both intervals must be at least 1 hour.
Parameter Description Scaling Type Select Interactive Resource Group. Resource Group The interactive resource group to use. Must have the multi-cluster feature disabled.
Each Interactive Resource Group scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
user_default.Desired Specifications The target computing resource specifications. Scaling Cycle The days on which the plan runs. Scaling Time (Cluster-specific) The time when computing resources are scaled to the desired specifications. Enabled Whether to enable the plan immediately. Enabled by default. Parameter Description Scaling Type Select EIU. Desired Specifications per EIU The target specifications for each elastic I/O unit (EIU). Cannot be lower than the single-node specifications of reserved storage resources. Scaling Cycle The days on which the plan runs. Scaling Time (Cluster-specific) The time when EIU resources are scaled to the desired specifications. Default Proportional Scaling for EIUs Disabled by default (EIU resources are scaled independently). When enabled, EIU resources are scaled by the same proportion as the associated Interactive Resource Group. Requires an Interactive Resource Group plan to be active. Enabled Whether to enable the plan immediately. Enabled by default. Click OK.
The plan appears on the Resource Scaling Plans tab. You can view Plan Name, Desired Specifications, Status, and Next Effective Time (Cluster-specific).
Data Warehouse Edition
Procedure
If running multiple plans on the same day, use intervals of at least 1 hour between plans.
Log in to the AnalyticDB for MySQL console. In the upper-left corner, select a region. In the left navigation pane, click Clusters, find the cluster, and click its ID.
In the left navigation pane, click Elastic Resource Scaling.
On the Resource Scaling Plans tab, click Create Plan.
In the Create Resource Scaling Plan panel, configure the following parameters.
Parameter Description Scaling Type The type of scaling plan. See Scaling plan types. Plan Name A name for the scaling plan. Resource Group The interactive resource group to use for scaling.
Each resource scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
USER_DEFAULT. For more information about resource groups, see Resource groups and Create and manage a resource group.Each Interactive Resource Group scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
user_default.Each resource scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
USER_DEFAULT. For more information about resource groups, see Resource groups and Create and manage a resource group.Each Interactive Resource Group scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
user_default.Each resource scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
USER_DEFAULT. For more information about resource groups, see Resource groups and Create and manage a resource group.Each Interactive Resource Group scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
user_default.Each resource scaling plan must be bound to a resource group. If the resource group is released, the scaling plan is bound to the default resource group
USER_DEFAULT. For more information about resource groups, see Resource groups and Create and manage a resource group.Effective Date The date from which the plan starts running. The exact effective time depends on when you create or modify the plan. See When does a plan take effect? Expiration Date The date after which the plan stops running. Scaling Time The time when resources are scaled to the desired specifications. Restoration Time The time when resources are scaled back to their original specifications. Scaled Resources The resources to add or set. The meaning varies by plan type: Scaling for Computing Resources — the amount to add on top of existing specs (for example, adding 16 cores and 64 GB to a cluster with 32 cores and 128 GB scales it to 48 cores and 192 GB). Default Proportional Scaling for Computing Resources and EIUs — the computing resources to add; elastic I/O resources are scaled by the same proportion (EIU scaling is triggered only when computing resources are scaled to at least 1.5x the current amount). Scaling for EIUs — the target specifications for elastic I/O resources (for example, setting to 16 cores and 128 GB on a cluster with 8 cores and 64 GB scales EIUs to 16 cores and 128 GB). Scaling Cycle The days on which the plan runs. Enabled Whether to enable the plan immediately. Enabled by default. Click OK.
Set up alerts for plan failures or delays
If resources are insufficient or an internal error occurs, scaling plans may be delayed or fail. To receive alert notifications, configure alert rules for the following events in CloudMonitor:
Instance:SystemMaintenance.Elastic:Delay — triggered when a scaling plan is delayed
Instance:SystemMaintenance.Elastic:Failed — triggered when a scaling plan fails
For setup instructions, see Manage event subscription policies (recommended).
FAQ
When does a resource scaling plan take effect?
Scaling plans don't take effect immediately after creation or modification — the system needs time to prepare resources in advance. The lead time varies by edition.
Enterprise Edition and Basic Edition
Enterprise Edition and Basic Edition: A new or modified plan takes effect within 1 hour.
For example, a plan is configured with Scaling Time 10:15:00 and Scaling Cycle every Wednesday:
Created at 9:00 → effective at 10:00 → first scaling at 10:15 the same day. Console shows Next Effective Time: 2024-09-18 10:15:00.
Created at 10:00 → effective at 11:00 → 10:15 has already passed → first scaling at 10:15 the following Wednesday. Console shows Next Effective Time: 2024-09-25 10:15:00.
Data Lakehouse Edition
Data Lakehouse Edition: Lead time depends on the plan type.
| Plan type | Lead time |
|---|---|
| Interactive Resource Group (no Default Proportional Scaling for EIUs active) | 10 minutes |
| Interactive Resource Group (Default Proportional Scaling for EIUs active) | 1 hour |
| EIU | 1 hour |
| Default Proportional Scaling for EIUs | Requires an active Interactive Resource Group plan to take effect |
For example, an Interactive Resource Group plan with Scaling Time 10:15:00 every Wednesday:
Default Proportional Scaling for EIUs is active, plan created at 10:00 → effective at 11:00 → 10:15 has passed → first scaling at 10:15 the following Wednesday (2024-09-25 10:15:00).
No Default Proportional Scaling for EIUs, plan created at 10:00 → effective at 10:10 → first scaling at 10:15 the same day (2024-09-18 10:15:00).
Data Warehouse Edition
Data Warehouse Edition: Effective time depends on when the plan is created or modified.
| Creation or modification time | Effective time |
|---|---|
| 00:00:00–23:00:00 | 00:00:00 the next day |
| 23:00:00–23:59:00 | 00:00:00 two days later |
Examples with Scaling Time 02:00:00 every Wednesday:
Created at 18:00 on September 24, 2024 (Tuesday) → effective at 00:00:00 on September 25 (Wednesday) → first scaling at 02:00:00 on September 25.
Created at 23:30 on September 24, 2024 (Tuesday) → effective at 00:00:00 on September 26 (Thursday) → first scaling at 02:00:00 on October 2 (the following Wednesday).
How do I schedule scale-out and scale-in for Enterprise Edition, Basic Edition, and Data Lakehouse Edition?
A single scaling plan cannot handle both scale-out and scale-in. Create two plans: one to scale out at peak time and one to scale in at off-peak time.
For example, to scale out at 06:00 and scale in at 22:00 every day:
Enterprise Edition
| Plan | Desired specifications per reserved resource set | Scaling cycle | Scaling time |
|---|---|---|---|
| Scale out | 36 ACUs | Daily | 06:00:00 |
| Scale in | 24 ACUs | Daily | 22:00:00 |
Basic Edition
| Plan | Desired specifications per reserved resource set | Scaling cycle | Scaling time |
|---|---|---|---|
| Scale out | 12 ACUs | Daily | 06:00:00 |
| Scale in | 8 ACUs | Daily | 22:00:00 |
Data Lakehouse Edition
| Plan | Scaling type | Desired specifications | Scaling cycle | Scaling time |
|---|---|---|---|---|
| Scale out | Interactive Resource Group | 32 ACUs | Daily | 06:00:00 |
| Scale in | Interactive Resource Group | 16 ACUs | Daily | 22:00:00 |
What's next
Manage a resource scaling plan — disable, modify, or delete existing plans
API reference
| Edition | API |
|---|---|
| Enterprise Edition, Basic Edition, Data Lakehouse Edition | CreateElasticPlan |
| Data Warehouse Edition | CreateElasticPlan |