All Products
Search

This Product

    AnalyticDB:Change a cluster from reserved to elastic mode

    Document Center

    AnalyticDB:Change a cluster from reserved to elastic mode

    Last Updated:Jun 17, 2026

    Change a cluster from reserved mode to elastic mode to reduce costs with tiered storage of hot and cold data and time-based scaling, and to isolate computing resources for different resource groups.

    Prerequisites

    • Your Alibaba Cloud account has no unpaid renewal orders.

    • Only clusters with minor version 3.1.3.9 or later support changing specifications across different instance families.

      Note

      To view and update the minor version, go to the Configuration Information section on the Cluster Information page in the AnalyticDB for MySQL console.

    • The cluster is in the Running state.

    Usage notes

    • Changing from reserved mode to elastic mode involves provisioning resources with new specifications, performing full and incremental data migration, and switching to the new cluster. The duration depends on the cluster specifications and data volume.

    • You cannot change other configurations while changing the ESSD performance level.

    • During the switchover, the original cluster enters a read-only state for 5 to 10 minutes.

      You can connect to the original cluster and run the following statement to specify a switchover time window. The following example sets the window to 23:00–23:30.

      SET adb_config REPLICATION_SWITCH_TIME_RANGE=`23:00, 23:30`;

      For information about how to connect to a cluster, see Connect to a cluster.

    • When you change a C32 cluster from reserved mode to elastic mode, the core count of a single node is reduced to 8. By default, a BUILD job uses 3 cores, which can increase the average CPU utilization. If the increased CPU utilization does not affect your services, you can ignore it. If your services are affected, scale up your cluster or Submit a ticket for technical support. For more information about BUILD jobs, see BUILD.

    Billing

    For more information, see Billing for specification changes.

    Procedure

    1. Log on to the AnalyticDB for MySQL console. In the upper-left corner, select the cluster's region. In the left-side navigation pane, click **Clusters**. On the **Data Warehouse Edition** tab, find the target cluster and click Scale Up or Scale Down in the **Actions** column.

    2. On the Upgrade/Downgrade page, select Elastic Mode and configure the parameters.

      Parameter

      Description

      Edition

      Fixed to Data Warehouse Edition. No selection is required.

      Edition

      Select Cluster Edition.

      Specifications

      Fixed as E32 and cannot be changed.

      Computing Resources

      Select the Computing Resources for the cluster. Computing resources are used for data computation. Increasing computing resources can improve query performance. We recommend provisioning computing resources with more CPU cores than Elastic I/O Units.

      EIU Capacity

      Select the EIU Capacity for the cluster. The specification you select here applies to a single node. A group of Elastic I/O Units consists of three nodes.

      EIUs (EIUs) are the basic units that measure the storage performance of an elastic mode cluster. You can scale storage resources independently by using EIUs. For more information, see Scale out Elastic I/O Units (EIUs).

      After scaling out Elastic I/O Units, the amount of hot data that can be locked by a single EIU increases. For more information, see Storage performance metrics based on EIUs. If you need to scale down, ensure that the hot data volume is less than the capacity of the downsized specification. If the hot data volume exceeds this capacity, we recommend that you move some data to cold storage before scaling down.

      EIUs

      Select the number of Elastic I/O Units.

      The number of units that you can purchase varies based on the Elastic I/O Unit specification.

      • If the specification is 8 cores and 64 GB, you can purchase up to 32 groups.

      • If the specification is 12 cores and 96 GB or 16 cores and 128 GB, you can purchase up to 16 groups.

      Note

      This parameter is supported only for clusters that are in elastic mode and have Computing Resources of 32 Cores, 128 GB or higher.

      ESSD Performance Level

      Select the disk level for the cluster. The capacity ranges for different disk levels are as follows:

      • PL0: 20 GiB to 65,536 GiB.

      • PL1: 20 GiB to 65,536 GiB.

      Important

      • When you change the ESSD performance level, you cannot change other configurations.

      • The amount of hot data must meet the minimum capacity requirement of the selected performance level when you change the ESSD performance level.

      • Changing the ESSD performance level affects the cost of hot storage space. The cost is calculated as: Unit price of storage space for the ESSD performance level * Hot storage usage * Duration. For unit prices, see Data Warehouse Edition Product Pricing.

    3. For a Subscription cluster, read and accept the Terms of Service, click Buy Now, confirm the order details and payment method, and then click . For a Pay-as-you-go cluster, read and accept the Terms of Service, and then click Buy Now.