Starting August 29, 2024, if the database proxy version of your ApsaraDB RDS for MySQL instance is 2.9.1 or later, you can configure the connection pooling and latency threshold settings for a database proxy endpoint that is set to read-only based on your business requirements.
Feature description
The database proxy feature allows you to configure the connection pooling and latency threshold settings.
You can select an appropriate type of connection pool for your RDS instance to reduce the connection frequency between your application and the RDS instance, the main thread overhead of the RDS instance, and the total number of connections to the RDS instance. For more information, see Configure the connection pooling feature.
You can specify a latency threshold for the required database proxy endpoint based on your business requirements. If the replication latency of a read-only RDS instance exceeds the threshold that you specify, requests are not forwarded to the read-only RDS instance.
If the database proxy version of your RDS instance is earlier than 2.9.1, you can configure the connection pooling and latency threshold settings only for a database proxy endpoint that is set to read/write.
If the database proxy version of your RDS instance is 2.9.1 or later, you can configure the connection pooling and latency threshold settings for a database proxy endpoint that is set to read/write or read-only.
Effective date
August 29, 2024
Billing rules
You are not charged additional fees for connection pooling and latency threshold settings. For more information, see Billing rules for database proxies.
Prerequisites
The RDS instance runs MySQL 5.6, MySQL 5.7, or MySQL 8.0.
The RDS instance runs RDS High-availability Edition or RDS Cluster Edition.
The RDS instance uses cloud disks or local disks.
The database proxy feature is enabled for the RDS instance, and the database proxy version of the RDS instance is 2.9.1 or later. For more information, see Enable the database proxy feature.
If the RDS instance runs RDS High-availability Edition, you must create at least one read-only RDS instance for the primary RDS instance. For more information about how to create a read-only RDS instance, see Create a read-only ApsaraDB RDS for MySQL instance.
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 left-side navigation pane, click Database Proxy.
In the Connection Information section of the page that appears, find the database proxy endpoint that you want to modify and click Modify Configuration in the Actions column.
In the dialog box that appears, configure connection pooling and latency threshold settings based on your business requirements.
Click OK.