AnalyticDB for MySQL allows you to schedule scaling of compute and storage resources by using resource scaling plans. This topic describes how to create a resource scaling plan.

Create a resource scaling plan for Data Lakehouse Edition (V3.0)

Usage notes

  • Manual configuration changes cannot be performed simultaneously with resource scaling plans. Before you perform a manual configuration change on a cluster, you must disable resource scaling plans for the cluster. After the manual configuration change is completed, you can enable resource scaling plans again. For more information about how to disable a resource scaling plan, see Manage a resource scaling plan.
  • An elastic I/O unit (EIU) scaling plan and a Default Proportional Scaling for EIUs scaling plan cannot be enabled at the same time.
  • If no Interactive Resource Group scaling plan is enabled, Default Proportional Scaling for EIUs scaling plans cannot take effect.

Types of scaling plans

Data Lakehouse Edition (V3.0) provides the following types of resource scaling plans:
  • Interactive Resource Group: Only computing resources are scaled based on the desired specifications that are specified in the scaling plan. This type is suitable for scenarios in which computing resources are insufficient.
  • Default Proportional Scaling for EIUs: If an Interactive Resource Group scaling plan takes effect, storage resources are scaled based on the default proportion. This type is suitable for scenarios in which resource requirements fluctuate predictably during peak and off-peak hours.
  • EIU: Only storage resources are scaled based on the desired specifications that are specified in the scaling plan. This type is suitable for scenarios in which storage resources are insufficient. For example, this type of scaling plans can be used if you want to import large amounts of data every day for business intelligence (BI) report analysis.

Procedure

  1. Log on to the AnalyticDB for MySQL console.
  2. In the upper-left corner of the page, select the region where the cluster resides.
  3. In the left-side navigation pane, click Clusters.
  4. On the Data Lakehouse Edition (V3.0) tab, find the cluster and click its Cluster ID.
  5. In the left-side navigation pane, choose Clusters > Resource Groups.
  6. On the Resource Scaling Plans tab of the Resource Groups page, click Create Plan in the upper-right corner.
  7. In the Create Resource Scaling Plan panel, configure the parameters that are described in the following table.
    Table 1. Scaling plan parameters for Data Lakehouse Edition (V3.0)
    ParameterDescription
    Plan NameThe name of the scaling plan. The name must meet the following requirements:
    • The name is 2 to 30 characters in length.
    • The name can contain letters, digits, and underscores (_).
    Start DateThe start date of the scaling plan.
    End DateThe end date of the scaling plan.
    Scaling TypeThe type of the scaling plan. Valid values:
    • Interactive Resource Group
    • EIU
      Note If you select EIU from the Scaling Type drop-down list, you can turn on Default Proportional Scaling for EIUs.
    Resource GroupThe interactive resource group to be used for the scaling plan.

    Each Interactive Resource Group scaling plan must be associated with a resource group. If the resource group is released, the scaling plan is associated with the user_default resource group.

    Note If you select Interactive Resource Group from the Scaling Type drop-down list, you must configure this parameter.
    Desired SpecificationsThe desired specifications.
    • An Interactive Resource Group scaling plan supports a maximum 144 AnalyticDB compute units (ACUs).
    • An EIU scaling plan supports a maximum of 192 ACUs.
    Note If you turn on Default Proportional Scaling for EIUs, this parameter is unavailable.
    Scaling CycleThe days on which you want to execute the scaling plan.
    Note If you turn on Default Proportional Scaling for EIUs, this parameter is unavailable.
    Scaling Time (Cluster-specific)The time when you want the system to start scaling the specified resources.
    Note
    • If you want to execute multiple scaling plans within the same day, we recommend that you schedule the scaling plans at an interval of not less than 1 hour.
    • If you turn on Default Proportional Scaling for EIUs, this parameter is unavailable.
    Default Proportional Scaling for EIUsSpecifies whether to enable a default proportional scaling plan for storage resources. By default, the scaling plan is disabled.

    If you want to make the Default Proportional Scaling for EIUs scaling plan take effect, you must create and enable an Interactive Resource Group scaling plan.

    EnabledSpecifies whether to enable the scaling plan. By default, the scaling plan is enabled. For more information about the effective rules for scaling plans, see the "Effective rules for a Data Lakehouse Edition (V3.0) scaling plan" section of this topic.
  8. Click OK.

Effective rules for a scaling plan

After you create or modify a scaling plan for a Data Lakehouse Edition (V3.0) cluster, the system determines the effective time of the plan based on the interval between the time that is specified by the Scaling Time (Cluster-specific) parameter in the scaling plan and the current time. The following table describes the effective rules for scaling plans.
Table 2. Effective rules for a Data Lakehouse Edition (V3.0) scaling plan
Interval between Scaling Time (Cluster-specific) and current timeEffective timeExample
Less than or equal to 30 minutes00:00:00 on the next day. After a scaling plan takes effect, the plan is executed at the time that is specified by the Scaling Time (Cluster-specific) parameter.
The current time is 10:00:00 on February 15, 2023 (Wednesday). A scaling plan is configured with the following parameters:
  • Start Date: 2023-02-15
  • End Date: 2023-02-22
  • Scaling Time (Cluster-specific): 10:20:00
  • Scaling Cycle: every Wednesday

Effective time: The plan takes effect at 00:00:00 on February 16, 2023. The cluster is scaled for the first time at 10:20:00 on February 22, 2023 (Wednesday).

Greater than 30 minutesThe current day. After a scaling plan takes effect, the plan is executed at the time that is specified by the Scaling Time (Cluster-specific) parameter.
The current time is 10:00:00 on February 15, 2023 (Wednesday). A scaling plan is configured with the following parameters:
  • Start Date: 2023-02-15
  • End Date: 2023-02-22
  • Scaling Time (Cluster-specific): 10:40:00
  • Scaling Cycle: every Wednesday

Effective time: The plan takes effect on February 15, 2023. The cluster is scaled for the first time at 10:40:00 on February 15, 2023 (Wednesday).

Create a resource scaling plan for Data Warehouse Edition (V3.0)

Prerequisites

  • The cluster is in Elastic mode for Cluster Edition.
  • The cluster has 32 cores or more.
  • If you want to use a default proportional scaling plan for computing resources and EIUs, the cluster must run minor version 3.1.3.2 or later.
  • If you want to use scaling plans for individual computing resources or EIUs, the cluster must run minor version 3.1.6.1 or later.
Note For more information about how to view the minor engine version of a cluster, see How can I view the version of an AnalyticDB for MySQL cluster? To update the minor engine version of a cluster, contact technical support.

Types of scaling plans

You can schedule scaling plans to scale up computing and storage resources of a Data Warehouse Edition (V3.0) cluster and then scale the resources back to the original specifications. This fully utilizes resources. Data Warehouse Edition (V3.0) provides the following types of resource scaling plans:
  • Scaling for Computing Resources: suitable for scenarios in which computing resources are insufficient.
  • Default Proportional Scaling for Computing Resources and EIUs: suitable for scenarios in which resource requirements fluctuate predictably during peak and off-peak hours.
  • Scaling for EIUs: suitable for scenarios in which storage resources are insufficient. For example, this type of scaling plans can be used if you want to import large amounts of data every day for BI report analysis.

Procedure

  1. Log on to the AnalyticDB for MySQL console.
  2. In the upper-left corner of the page, select the region where the cluster resides.
  3. In the left-side navigation pane, click Clusters.
  4. On the Data Warehouse Edition (V3.0) tab, find the cluster and click its Cluster ID.
  5. In the left-side navigation pane, click Elastic Resource Scaling.
  6. On the Resource Scaling Plans tab of the Elastic Resource Scaling page, click Create Plan in the upper-right corner.
    1
  7. In the Create Resource Scaling Plan panel, configure the parameters that are described in the following table.
    Table 3. Scaling plan parameters for Data Warehouse Edition (V3.0)
    ParameterDescription
    Scaling TypeThe type of the scaling plan.
    Important
    • If you want to use a default proportional scaling plan for computing resources and EIUs, the cluster must run minor version 3.1.3.2 or later.
    • If you want to use scaling plans for individual computing resources or EIUs, the cluster must run minor version 3.1.6.1 or later.
    Plan NameThe name of the scaling plan. The name must meet the following requirements:
    • The name is 2 to 30 characters in length.
    • The name can contain letters, digits, and underscores (_).
    Resource GroupThe resource group to be associated with the scaling plan.

    Each scaling plan must be associated with a resource group. If the resource group is released, the scaling plan is automatically re-associated with the USER_DEFAULT resource group. For more information about resource groups, see Resource group overview (Data Warehouse Edition) and Create a resource group.

    Start DateThe start date of the scaling plan.
    End DateThe end date of the scaling plan.
    Scaling TimeThe time when you want the system to start scaling the specified resources. Select the time on the hour.
    Note If you want to execute multiple scaling plans within the same day, we recommend that you schedule the scaling plans at an interval of not less than 1 hour.
    Restoration TimeThe time when you want the system to scale the resources back to the original specifications. Select the time on the hour.
    Scaled ResourcesThe specifications of resources to be scaled up, which can be up to eight times the current specifications.

    For example, if the cluster has 32 cores and 128 GB memory, you can select a maximum of 256 cores and 1,024 GB memory. After scaling, the cluster has 288 cores and 1,152 GB memory.

    Scaling CycleThe days on which to execute the scaling plan. You must select at least one day per week.
    EnabledSpecifies whether to enable the scaling plan. By default, the scaling plan is enabled. For more information about the effective rules for scaling plans, see the "Effective rules for a Data Warehouse Edition (V3.0) scaling plan" section of this topic.
  8. Click OK.

Effective rules for a scaling plan

After you create or modify a scaling plan for a Data Warehouse Edition (V3.0) cluster, the system determines the effective time of the plan based on the time when the plan is created or modified. The following table describes the effective rules for a scaling plan.
Table 4. Effective rules for a Data Warehouse Edition (V3.0) scaling plan
Creation or modification timeEffective timeExample
00:00:00 to 23:00:0000:00:00 on the next day. After a scaling plan takes effect, the plan is executed at the specified time.
The creation time of a scaling plan is 18:00:00 on May 25, 2021 (Tuesday). The scaling plan is configured with the following parameters:
  • Start Date: 2021-05-25
  • End Date: 2021-06-03
  • Scaling Time: 02:00:00
  • Scaling Cycle: every Wednesday

Effective time: The plan takes effect at 00:00:00 on May 26, 2021 (Wednesday). The cluster is scaled for the first time at 02:00:00 on May 26, 2021 (Wednesday).

23:00:00 to 23:59:0000:00:00 on the third day. After a scaling plan takes effect, the plan is executed at the specified time.
The creation time of a scaling plan is 23:30:00 on May 25, 2021 (Tuesday). The scaling plan is configured with the following parameters:
  • Start Date: 2021-05-25
  • End Date: 2021-06-03
  • Scaling Time: 02:00:00
  • Scaling Cycle: every Wednesday

Effective time: The plan takes effect at 00:00:00 on May 27, 2021 (Thursday). The cluster is scaled for the first time at 02:00:00 on June 2, 2021 (Wednesday).