Configuration items for an ApsaraDB RDS for MySQL instance - ApsaraDB RDS

This topic describes the configuration items for an ApsaraDB RDS for MySQL instance.

Computing and storage

Instance type

Description

Change method

You can change the instance type for all instances.

Note

Some legacy instance types cannot be changed directly. In this case, perform the following steps to change the instance type:

Create a new instance and select the destination instance type.
Migrate data from the original instance to the new instance
Release the original instance

Change configurations

Configure automatic performance scaling

Storage type

Description

Change method

The following storage type changes are supported:

For an instance that runs MySQL 8.0 or 5.7 on High-availability Edition or Basic Edition with standard SSDs, you can change the storage type to enterprise SSD (ESSD).
For an instance that runs MySQL 8.0 or 5.7 on High-availability Edition with premium local disks, you can change the storage type to ESSD.
When you upgrade a MySQL 5.7 instance from Basic Edition with standard SSDs to High-availability Edition, you can also change the storage type to premium local disks.
For an instance that uses an ESSD with at least 40 GB of storage, you can change the storage type to premium performance disk.
For Basic Edition, you can change the storage type from PL0 ESSD to PL1 ESSD, but not from PL1 ESSD to PL0 ESSD.
For nodes of High-availability Edition and Cluster Edition instances, you can switch the storage type between PL1, PL2, and PL3 ESSDs.

Upgrade from standard SSD to ESSD

Change from premium local disk to cloud disk

Upgrade from Basic Edition to High-availability Edition

Change from ESSD to premium performance disk

Storage capacity

Operation type

Description

Change method

Scale-out

Increase the storage capacity by at least 5 GB. The new capacity cannot exceed the maximum storage capacity of the current instance type. For more information, see Primary instance types.

Note

For instances that use cloud disks and are not Basic Edition, you can increase the storage capacity online. In most cases, this operation does not cause transient connections.

Change configurations

Configure automatic storage expansion

Scale-in

Premium local disks: For High-availability Edition instances that use local disks, you can reduce the storage capacity.
Cloud disks: For Basic Edition, High-availability Edition, and Cluster Edition instances, you can reduce the storage capacity within the same edition and architecture. The minimum storage capacity to which you can reduce is calculated using the formula min{Used storage × 1.3, Used storage + 400 GB}. The new capacity cannot be smaller than the minimum storage capacity supported by the current instance type. The storage capacity can be adjusted in 5 GB increments.
Note
- For Cluster Edition instances that use cloud disks, storage capacity reduction is currently supported only in the Singapore region. This feature is being rolled out to other regions. For the latest information, see the change configuration page.
- Currently, you can reduce the storage capacity only for instances that run RDS for MySQL 5.7 or 8.0 with a minor engine version of 20210430 or later.
Examples of storage capacity reduction
Assume an instance uses a PL1 ESSD with 2,000 GB of storage. The minimum storage capacity for the instance type is 20 GB. The range to which you can reduce the storage capacity varies based on the storage usage:
If 10 GB of storage is used, the value calculated by the formula is min{10 × 1.3, 10 + 400} = 13 GB. Because 13 GB is less than 20 GB, the minimum capacity to which you can reduce is 20 GB.
If 500 GB of storage is used, the value calculated by the formula is min{500 × 1.3, 500 + 400} = 650 GB. The minimum capacity to which you can reduce is 650 GB.
If 1,500 GB of storage is used, the value calculated by the formula is min{1500 × 1.3, 1500 + 400} = 1900 GB. The minimum capacity to which you can reduce is 1,900 GB.

Premium local disks: Change configurations

Cloud disks: Reduce the capacity of an ESSD

Note

The storage capacity of a read-only instance must be greater than or equal to the storage capacity of its primary instance.
If the storage capacity range of the current instance type does not meet your requirements, you can select another instance type.

Region and zone

Configuration item

Description

Change method

Region

You cannot change the region of an instance after it is created. To deploy your database service in a different region, create an instance in the destination region. Then, migrate data using Data Transmission Service (DTS). After the migration, modify the endpoint in your application. After you confirm that your business runs as expected, release the original instance.

Migrate data

Zone

You can migrate an instance to another zone in the same region. After the migration, all properties, configurations, and endpoints of the instance remain unchanged.

When you upgrade an RDS for MySQL 5.7 instance from High-availability Edition to RDS Enterprise Edition (formerly Finance Edition), you must change the zone of the instance.

Note

You cannot migrate a Cluster Edition instance across zones.
Migrating an instance across zones requires data migration. The more data you have, the longer the migration takes.

Migrate an instance across zones

RDS edition and product type

Configuration item

Description

Change method

Product Series

Only the following RDS edition changes are supported:

MySQL 5.6 RDS Enterprise Edition: Change to High-availability Edition.
MySQL 8.0 and 5.7 Basic Edition: Change to High-availability Edition.
MySQL 8.0 and 5.7 High-availability Edition: Change to Cluster Edition.

Note

Changes to the RDS edition are not supported in other scenarios. To change the RDS edition in other scenarios, perform the following steps:

Create a new instance and select the destination edition.
Migrate data from the original instance to the new instance
Release the original instance

Change from RDS Enterprise Edition to High-availability Edition for MySQL 5.6

Upgrade from Basic Edition to High-availability Edition

Upgrade from High-availability Edition to Cluster Edition

Product type

High-availability and Cluster editions: You can switch between Standard Edition and Yitian Edition.
Basic Edition: You can only change from Yitian Edition to Standard Edition.

Note

If you cannot select the destination product type during the change, resources for that type may not be available for purchase in the instance's current zone.
You can go to the instance purchase page to view the available zones for the target type, use the Migrate Zone feature to migrate the current instance to a target zone, and then change the configuration.
If you change the product type, ensure that the new minor engine version is the same as or later than the current minor engine version. You cannot change the product type if the new minor engine version is earlier than the current one.

Change configurations

Networking

Configuration item	Description	Change method
VPC and vSwitch	For some instances, you can switch the VPC and vSwitch.	Switch the VPC and vSwitch

Primary and secondary instances

Configuration item

Description

Change method

Primary/secondary relationship

You can perform automatic or manual primary/secondary failovers. After a failover, the original primary instance becomes the secondary instance.

Manage primary/secondary failovers

Data replication mode

Change the data replication mode between the primary and secondary instances to improve database availability.

Query and change the data replication mode

Instance parameters

Description	Change method
Modify some parameters of your instance to better meet your business needs.	Set instance parameters or Use a parameter template

Database engine version

Description

Change method

The following major version upgrades are supported in the console:

RDS for MySQL 5.7 → RDS for MySQL 8.0
RDS for MySQL 5.6 → RDS for MySQL 5.7
RDS for MySQL 5.5 → RDS for MySQL 5.6

Note

You cannot skip major versions during an upgrade. For example, you cannot directly upgrade from RDS for MySQL 5.5 to RDS for MySQL 8.0.

Upgrade the database engine version

Maintenance window

Description	Change method
Change the maintenance window of your instance.	Set a maintenance window

Billing method

Description

Change method

You can switch the billing method of an instance between pay-as-you-go and subscription.

Change from pay-as-you-go to subscription

Change from subscription to pay-as-you-go