ApsaraDB RDS:RDS High-availability Edition

RDS High-availability Edition is a widely used edition. RDS instances of this edition are deployed in a primary/secondary architecture to deliver highly available services. This edition is suitable for more than 80% of use cases in various industries, such as Internet, IoT, online retail, logistics, and gaming.

Topology

Benefits

• High availability

  In RDS High-availability Edition, the mode that is used to synchronize the data of the primary RDS instance to the secondary RDS instance varies based on the parameter template that you select. The semi-synchronous mode or asynchronous mode is used to synchronize data. If the primary RDS instance becomes inaccessible, your database system fails over to the secondary RDS instance.

  Note

  • After an update that is initiated by your application is complete on the primary RDS instance, the related log is synchronized to the secondary RDS instance. After the secondary RDS instance receives the log, the transaction that is used to perform the update is considered committed. Your database system does not need to wait for the secondary RDS instance to replay the log. If the secondary RDS instance is unavailable or a network interruption occurs between the primary and secondary RDS instances, the semi-synchronous mode degrades to the asynchronous mode.

  • After an add, delete, or modify operation that is initiated by your application is complete on a primary RDS instance, the primary RDS instance immediately responds to the application. At the same time, the primary RDS instance replicates the added, deleted, or modified data to the secondary RDS instance. In asynchronous mode, the workloads on the primary RDS instance run as expected even if the secondary RDS instance is unavailable. However, if the primary RDS instance is unavailable, errors may occur due to data inconsistencies between the primary and secondary RDS instances.

  In RDS High-availability Edition, the primary and secondary RDS instances can be deployed in the same zone or different zones in the same region. If the primary and secondary RDS instances are deployed in different zones, cross-zone disaster recovery can be implemented, and the availability of your database system is improved.

  Note

  If the secondary RDS instance becomes inaccessible, data of the primary RDS instance is backed up in real time. When a backup is near completion, the FLUSH TABLE WITH READ LOCK (FTWRL) statement is executed. This triggers a global lock that is held for up to 5 seconds. When the global lock is held, the primary RDS instance is in read-only mode.

• Comprehensive functionality

  RDS High-availability Edition provides a complete suite of features, such as auto scaling, backup and restoration, performance optimization, read/write splitting, and SQL Explorer. The SQL Explorer feature stores the logs of all executed statements for up to five years. You can use the logs to trace operations performed on your databases, which helps ensure the security of your data.

Limits

For performance purposes, the primary and secondary RDS instances must be deployed in the same region.

Upgrade the RDS edition of an RDS instance to RDS High-availability Edition

RDS instances that run RDS Basic Edition are deployed in a standalone architecture. Due to the lack of a hot standby, your workloads may experience extended periods of downtime when the RDS instance fails. This also happens when you change the specifications or upgrade the database engine. If you require high service availability, we recommend that you use RDS High-availability Edition.

Create an RDS instance

FAQ

• Can I establish a direct connection to my secondary RDS instance?

  No, direct connections cannot be established to secondary RDS instances. Direct connections can only be established to the primary RDS instance. A secondary RDS instance serves as a standby and cannot be accessed externally.

• Can I downgrade an RDS instance from RDS High-availability Edition to RDS Basic Edition?

  No, you cannot downgrade an RDS instance from RDS High-availability Edition to RDS Basic Edition. If you want to downgrade an RDS instance from RDS High-availability Edition to RDS Basic Edition, you can purchase an RDS instance that runs RDS Basic Edition and migrate the data of your original RDS instance to the new RDS instance. Then, release your original RDS instance. For more information, see Use DTS to migrate data between ApsaraDB RDS for PostgreSQL instances and Release or unsubscribe from an ApsaraDB RDS for PostgreSQL instance.

• How do I change the data replication mode of my RDS instance on RDS High-availability Edition?

  For more information, see Query and change the data replication mode.

• I am using RDS High-availability Edition. Is the data replication mode changed to the asynchronous mode if the secondary RDS instance handles heavier workloads than the primary RDS instance?

  Yes, if the secondary RDS instance handles heavier workloads than the primary RDS instance, the data replication mode is changed to the asynchronous mode. For more information, see Query and change the data replication mode.