All Products
Search

This Product

    AnalyticDB:Purchase, configuration change, and upgrade

    Document Center

    AnalyticDB:Purchase, configuration change, and upgrade

    Last Updated:May 26, 2025

    This topic provides answers to some frequently asked questions about purchase, configuration change, and upgrade in AnalyticDB for MySQL.

    If no edition is specified in a question, the question applies only to AnalyticDB for MySQL Data Warehouse Edition clusters.

    FAQ overview

    How are Enterprise Edition and Basic Edition clusters billed?

    When you purchase an Enterprise Edition or Basic Edition cluster, you need to pay fees only for reserved resources on the buy page. The fees of other billable items, such as storage and elastic resources, are billed on a pay-as-you-go basis when you use the cluster. For information about the billing rules of Enterprise Edition and Basic Edition, see Billable items of Enterprise Edition and Basic Edition.

    For example, you purchase a pay-as-you-go Enterprise Edition cluster that supports single-zone deployment in the China (Hangzhou) region to store 360 GB of data. The cluster has 3 reserved resource nodes, each with specifications of 8 AnalyticDB compute units (ACUs). The 360 GB of data includes 100 GB of hot data and 260 GB of cold data. The following table describes the fees of the cluster.

    Billable item

    Fee

    Reserved resources

    USD 0.04615 per ACU-hour × 8 ACUs × 3 nodes × 1 hour = USD 1.1076

    Hot data storage

    USD 0.00022 per GB-hour × 100 GB × 1 hour × 2 = USD 0.044

    Cold data storage

    USD 0.000028 per GB-hour × 260 GB × 1 hour = USD 0.00728

    Total fees per hour = USD 1.1076 + USD 0.044 + USD 0.00728 = USD 1.15888.

    What are the differences between Enterprise Edition and Basic Edition?

    Both Enterprise Edition and Basic Edition provide capabilities in elastic mode, such as resource group isolation, elastic resource scaling, and tiered storage of hot and cold data, and support capabilities in reserved mode, such as high throughput, real-time writes and high-concurrency, real-time queries. However, Enterprise Edition is built on a multi-replica storage architecture and provides high availability, while Basic Edition is built on a single-replica storage architecture and does not provide high availability. For more information, see Editions.

    What are the differences between Data Warehouse Edition and Data Lakehouse Edition?

    By leveraging the high-performance real-time analysis of Data Warehouse Edition, Enterprise Edition and Data Lakehouse Edition provide cost-effective batch processing and machine learning capabilities to help process large amounts of data, decouple computing and storage, and reduce costs. The data lakehouse architecture prevents consistency and timeliness issues that may be caused by data synchronization. For more information, see Editions.

    What are the differences between Data Warehouse Edition in elastic mode and Data Warehouse Edition in reserved mode?

    • The billing methods of storage resources are different in the two modes.

      • In reserved mode, you must specify the required storage capacity when you create a cluster. You are charged based on the specified storage capacity.

      • In elastic mode, you do not need to specify the storage capacity when you create a cluster. You are charged based on the storage usage.

        For example, if you purchase a pay-as-you-go cluster and the storage usage on a specific day is 100 GB, you are charged for the storage resources based on the following formula: 100 GB × Usage duration. In elastic mode, AnalyticDB for MySQL imposes a minimum charge based on 20 GB of storage. You are charged for 20 GB of data storage even if the storage usage is less than 20 GB.

    • In elastic mode, computing resources are separated from storage resources. Computing resources are used to process and compute data. Storage resources are used to read and write data. This way, you can identify whether performance bottlenecks of your workloads are caused by computing resources or storage resources, and scale your resources accordingly to reduce costs.

    What are the purposes of elastic I/O resources?

    Elastic I/O resources are bundled into units and sold as elastic I/O units (EIUs) to measure the storage performance of AnalyticDB for MySQL clusters. Real-time data and hot data are stored in EIUs to support high workloads that are caused by data import and index building. For more information, see Scale out elastic I/O resources.

    Why am I charged pay-as-you-go fees for my subscription cluster?

    When you create an AnalyticDB for MySQL cluster, what you pay are subscription fees for basic resources. However, you may require additional storage and elastic resources to store your data and scale up resources. These resources are billed on a pay-as-you-go basis and are reflected in your bills. For more information about billing rules, see Billable items.

    Can I shut down an AnalyticDB for MySQL cluster?

    No, you cannot shut down an AnalyticDB for MySQL cluster. To reduce costs, you can purchase storage plans and ACU-hour plans to offset the storage costs and resources that are consumed by clusters. The resources include reserved computing resources, reserved storage resources, and elastic resources.

    How do I check whether charging for an AnalyticDB for MySQL cluster stops?

    After you delete an AnalyticDB for MySQL cluster, charging for the cluster stops immediately. You can log on to the AnalyticDB for MySQL console, select a region in the upper-left corner of the console, and then check whether the cluster exists. If the cluster is not displayed, it indicates that the cluster is deleted.

    How do I retain and stop charging for a cluster that is no longer used?

    • For a subscription cluster, you have already paid for the reserved resources on the buy page. However, you may incur additional pay-as-you-go charges for elastic resources, storage, caches, or backups during cluster usage. To retain the cluster without incurring additional fees, delete or shut down operations that may lead to pay-as-you-go charges based on the billable items.

    • A pay-as-you-go cluster is billed hourly. To stop charging for the cluster, delete it.

    What do I do if my AnalyticDB for MySQL cluster is locked?

    If your AnalyticDB for MySQL Data Warehouse Edition cluster in elastic mode is locked because the amount of hot data that is stored in an EIU exceeds 8 TB, scale up your elastic I/O resources at the earliest opportunity.

    In what scenarios may the availability of an AnalyticDB for MySQL cluster be affected?

    The availability of an AnalyticDB for MySQL cluster may be affected when failures occur on the cluster or when the cluster undergoes configuration changes or version upgrades.

    How do I query the minor version of an AnalyticDB for MySQL cluster?

    1. Connect to an AnalyticDB for MySQL cluster.

    2. Execute the following statement: 

      select adb_version();

    3. Obtain the minor version of the cluster from the query result.

      Sample result:

      +----------------+----------------+---------------------+-------------+---------------------+
| source_version | rpm_version    | build_date          | revision_id | revision_date       |
+----------------+----------------+---------------------+-------------+---------------------+
| 3.1.4.10       | 20210809205222 | 2021-08-09 20:52:22 | 97b631a     | 2021-08-09 20:32:04 |
+----------------+----------------+---------------------+-------------+---------------------+

    How long does it take to complete an upgrade in AnalyticDB for MySQL? Does an upgrade affect my business?

    In most cases, an upgrade requires approximately 30 minutes to 2 hours to complete. The required time varies based on the cluster specifications and the data volume. Your business may encounter transient connections during the upgrade. Make sure that your application is configured to automatically reconnect to your cluster. If your business requires a high success rate for queries, we recommend that you perform upgrades during nighttime or off-peak hours.

    Does a configuration change on an AnalyticDB for MySQL cluster affect the number of shards?

    A configuration change on an AnalyticDB for MySQL cluster does not affect the number of shards.

    How do I restart an AnalyticDB for MySQL cluster?

    You cannot restart an AnalyticDB for MySQL cluster in the console. To restart the cluster, submit a ticket.