This topic describes how to upgrade an ApsaraDB RDS instance that runs MySQL 8.0 or MySQL 5.7 from RDS High-availability Edition to RDS Cluster Edition. Compared with RDS High-availability Edition, RDS Cluster Edition is more cost-effective, flexible, and reliable.
Scenarios
If you require more flexible deployment, finer-grained monitoring, and more reliable disaster recovery at lower costs, you can upgrade your RDS instance from RDS High-availability Edition to RDS Cluster Edition. RDS Cluster Edition for MySQL provides the following features: readable secondary nodes, node addition and deletion, multi-zone disaster recovery, node-level monitoring, and node topology management. Compared with RDS Basic Edition and RDS High-availability Edition, RDS Cluster Edition for MySQL is more cost-effective, flexible, and reliable. For more information, see RDS Cluster Edition.
Prerequisites
The RDS instance runs MySQL 8.0 or MySQL 5.7 on RDS High-availability Edition.
NoteYou can go to the Basic Information page of your RDS instance to view the RDS edition.
No read-only RDS instances are attached to the RDS instance.
The database proxy feature is disabled for the RDS instance.
The RDS instance uses the enhanced SSD (ESSD) storage type.
NoteIf the RDS instance uses the standard SSD storage type, you must upgrade the storage type to ESSD. For more information, see Upgrade the storage type of an ApsaraDB RDS for MySQL instance from standard SSDs to ESSDs.
The RDS instance uses the x86 architecture.
The minor engine version of the RDS instance is 20201031 or later.
NoteFor more information, see Update the minor engine version.
Impacts
The upgrade may trigger data migration, which may require 10 to 20 minutes to complete. After the migration is complete, ApsaraDB RDS switches your workloads at the specified switching time. During the switchover, a 30-second transient connection occurs. Make sure that your application is configured to automatically reconnect to your RDS instance.
NoteAfter the upgrade, the endpoint of the RDS instance remains unchanged. You do not need to modify application configurations.
After the upgrade, you cannot downgrade your RDS instance to RDS High-availability Edition.
Billing rules
For more information about the fees for the upgrade, see Specification changes.
Procedure
Read and select Terms of Service and click Pay Now. In the dialog box that appears, confirm the instance information before and after the specification change and click Continue to complete the payment.
On the Basic Information section of the Basic Information page, check whether the upgrade is successful. If the value of the Instance Type and Edition parameter of the RDS instance is Regular Instance (Cluster Edition), the upgrade is successful.
Related operations
Operation | Description |
You can call the ModifyDBInstanceSpec operation to upgrade the RDS edition of an instance to RDS Cluster Edition. When you call this operation, you must set the DBInstanceClass parameter to a value that specifies the new instance type supported by RDS Cluster Edition and set the Category parameter to Cluster. You can configure other parameters based on your business requirements. | |
You can call the DescribeDBInstanceAttribute operation to check whether the value of the Category parameter is Cluster. If the value of the Category parameter is Cluster, the upgrade is successful. |