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. RDS Cluster Edition is more cost-effective, flexible, and reliable than RDS High-availability Edition.
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 ApsaraDB RDS for MySQL provides the following features: readable secondary nodes, node addition and deletion, multi-zone disaster recovery, node-level monitoring, and node topology management. RDS Cluster Edition is more cost-effective, flexible, and reliable than RDS High-availability Edition. 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) or general 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 from standard SSDs to ESSDs.
The RDS instance uses the standard product type.
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, the system switches your workloads at the specified switching time. During the switchover, an instance switchover occurs. Make sure that your application is configured to automatically reconnect to your RDS instance. For more information about the impacts of an instance switchover, see Impacts of an instance switchover.
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 Type and Edition parameter of the RDS instance is Regular Instance (Cluster Edition), the upgrade is successful.
Related operations
Operation | Description |
Changes the specifications of an instance. 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. | |
Queries the information about an instance. You can call the DescribeDBInstanceAttribute operation and check the value of the Category parameter in the response to check whether the upgrade is successful. If the value of the Category parameter is Cluster, the upgrade is successful. |