Upgrade a standard SSD to an ESSD
Compared to standard SSDs, PL1 ESSDs are built on a next-generation distributed block storage architecture and deliver higher IOPS, greater throughput, and more stable I/O performance. In most regions, the cost of a PL1 ESSD is the same as that of a standard SSD. You can upgrade the storage type from a standard SSD to a PL1 ESSD in the console for a better price-to-performance ratio.
Prerequisites
-
The instance is in the Running state.
-
The instance is one of the following types:
-
An ApsaraDB RDS for MySQL 8.0 instance of High-availability Edition or Basic Edition that uses a standard SSD
-
An ApsaraDB RDS for MySQL 5.7 instance of High-availability Edition or Basic Edition that uses a standard SSD
-
-
For a Basic Edition instance, the minor engine version is 20201031 or later. For more information, see Upgrade the minor engine version.
This topic describes how to upgrade from a standard SSD to an ESSD. To change a local SSD to an ESSD, see Change a local SSD to an ESSD.
Performance comparison
PL1 ESSDs and standard SSDs have similar costs but differ significantly in performance. The following table describes the performance metrics.
|
Metric |
ESSD (PL1) |
Standard SSD |
|
Maximum capacity per disk (GiB) |
20 to 64,000 |
6,000 |
|
Maximum IOPS |
50,000 |
25,000 |
|
Maximum throughput (MB/s) |
350 |
300 |
|
Per-disk IOPS formula |
min(1,800 + 50 × Capacity, 50,000) |
min(1,800 + 30 × Capacity, 25,000) |
|
Per-disk throughput formula (MB/s) |
min(120 + 0.5 × Capacity, 350) |
min(120 + 0.5 × Capacity, 300) |
|
Average single-stream random write latency (ms) |
0.2 |
0.5 to 2 |
Fees
The upgrade involves the following fees:
-
Backup fees: To ensure data security, the system creates a temporary full backup of the instance and retains the backup for seven days. This backup is subject to fees. For more information, see Backup fees.
-
ESSD fees: Upgrading the storage type may incur a fee that varies based on the region of your instance. You can view the fee details when you change the specifications.
Impacts
-
The storage type upgrade causes a transient disconnection that lasts approximately 15 seconds. Perform this operation during off-peak hours and ensure that your application is configured with an automatic reconnection mechanism.
-
During the storage type upgrade, you cannot perform instance-level operations, such as changing specifications, upgrading the engine version, or migrating the instance across availability zones.
Procedure
Go to the Instances page. In the top navigation bar, select the region in which the RDS instance resides. Then, find the RDS instance and click the ID of the instance.
-
In the Basic Information section, click Upgrade Storage Type to the right of Storage Type.
NoteIf the Upgrade Storage Type button is not displayed, check whether your instance meets all the requirements that are described in the Prerequisites section. If the instance meets all the prerequisites but the button is still not displayed, ESSDs are not available in the region.
-
On the Change Specifications tab, select the terms of service, and click Pay Now in the lower-right corner to complete the payment.
The instance enters the Upgrading/Downgrading state. When the instance state changes back to Running, the upgrade is complete.
FAQ
-
Q: Why am I unable to select an ESSD?
A: In some cases, an availability zone may have insufficient resources or temporarily stop selling ESSDs. If your instance is in such an availability zone, you must first upgrade the minor engine version of the instance, migrate the instance to an availability zone where ESSDs are available, and then upgrade the storage type to ESSD.
-
Q: When I upgrade the storage type of a primary instance, is the storage type of its read-only instances automatically upgraded?
A: No, the storage type of read-only instances is not automatically upgraded. You must manually upgrade the storage type of each read-only instance by repeating the procedure in this topic.
-
Q: Does changing the configuration affect my workloads?
A: For more information, see the Impacts section of this topic.
-
Q: Does the instance endpoint change after the storage type is changed?
A: The instance endpoint, such as
rm-bpxxxxx.mysql.rds.aliyuncs.com, does not change, but the IP address that is mapped to the endpoint may change. We recommend that you use the endpoint instead of the IP address in your applications. -
Q: What affects the time required to change the storage type of an ApsaraDB RDS for MySQL instance?
A: For more information, see What affects the time required to change the specifications of an ApsaraDB RDS for MySQL instance?.
Related APIs
|
API |
Description |
|
Changes the specifications of an ApsaraDB RDS instance. |