All Products
Search
Document Center

ApsaraDB RDS:Change the storage type from ESSD to general ESSD

Last Updated:Jul 24, 2024

After you enable the I/O burst feature of general ESSDs for an ApsaraDB RDS for MySQL instance, the IOPS of general ESSDs is no longer limited by the maximum IOPS. This improves the I/O performance of the RDS instance to handle workload bursts during peak hours, and you do not need to expand the storage capacity. To optimize I/O performance, you can upgrade ESSDs of any performance level (PL) to general ESSDs. This topic describes how to change the storage type of an RDS instance from ESSD to general ESSD.

Prerequisites

The storage type of the RDS instance is ESSD.

Impacts

When you change the storage type of an RDS instance from ESSD to general ESSD, the change immediately takes effect and causes no transient connections. In most cases, your workloads are not adversely affected. In some cases, the IOPS of the RDS instance may fluctuate. We recommend that you perform this operation during off-peak hours.

Usage notes

  • The storage type change from ESSD to general ESSD takes effect based on the RDS edition of an RDS instance. If the RDS instance runs RDS Cluster Edition, the change takes effect on all primary and secondary nodes in the RDS cluster. If the RDS instance runs RDS High-availability Edition, the change takes effect on the primary and secondary RDS instances. If the RDS instance runs RDS Basic Edition, the change takes effect on the RDS instance. The change does not affect the storage types of read-only RDS instances. To change the storage type of a read-only RDS instance, go to the instance details page to perform the required operations.

  • When you change the storage type from ESSD to general ESSD, you can configure only the I/O burst feature. Other configurations cannot be modified.

  • After you change the storage type from ESSD to general ESSD, you cannot change the storage type to another type. Proceed with caution.

  • Before you change the storage type from ESSD to general ESSD, make sure that no backup tasks are in progress for the RDS instance. If backup tasks are in progress, the time that is required to change the storage type is prolonged.

Billing rules

  • The unit prices of an ESSD and a general ESSD are different. ESSDs come in the following PLs: PL1, PL2, and PL3. The price difference for the storage type change is displayed on the Change Specifications page.

  • Within a specific period of time, if an RDS instance handles a large number of I/O operations for a shorter period of time, general ESSDs are more cost-effective than PL1 ESSDs, PL2 ESSDs, and PL3 ESSDs.

  • General ESSD fee = Fee for the storage capacity that you purchase for your RDS instance + I/O burst fee + I/O acceleration fee + Data archiving fee For more information, see What are general ESSDs?

Procedure

  1. Log on to the ApsaraDB RDS console and go to the Instances page. In the top navigation bar, select the region in which your RDS instance resides. Then, find the RDS instance and click the ID of the RDS instance.

  2. In the Basic Information section of the page that appears, click Upgrade Storage Type to the right of Storage Type.

  3. On the Change Specifications page, read and select Terms of Service and click Pay Now to complete the payment.

    Note
    • You can turn on I/O Burst. By default, the feature is disabled.

    • The status of the RDS instance changes to Upgrading. When the status of the RDS instance changes to Running, the upgrade is complete.

References

Related operations

Operation

Description

ModifyDBInstanceSpec

When you change the storage type of an RDS instance from ESSD to general ESSD, take note of the following items:

  • Make sure that the original storage type is ESSD and DBInstanceStorageType parameter is set to general_essd.

  • The BurstingEnabled parameter is used to manage the I/O burst feature. The value true indicates that the feature is enabled. The value false indicates that the feature is disabled.

  • Do not modify other parameters, such as the instance type and storage capacity.