RDS for MySQL database proxy minor version release notes - ApsaraDB RDS

RDS for MySQL periodically updates the minor version of its database proxy. This topic contains the release notes for each minor engine version of the RDS for MySQL database proxy, which include new features, improvements, and bug fixes. This topic also describes how to view the minor engine version.

Note

To upgrade the minor version of the database proxy, see Upgrade the minor engine version of a database proxy.
For information about the minor versions of the RDS for MySQL kernel, see AliSQL kernel minor version release notes.

View the minor engine version of the proxy

View the current version: On the Database Proxy page of the instance, the minor version is displayed under Basic Information > Proxy Minor Version.
View available upgrades: Click Upgrade next to Proxy Minor Version to view the Upgradable Versions.

Note

If the database proxy is running the latest version, the Upgrade button is not displayed.
You can also call an API operation to view the minor version of the proxy. For more information, see Query the details of a database proxy.

Minor version update descriptions

Note

The following table lists only the mainstream versions of the database proxy and does not include all released versions. The version number of your proxy may not be in this list.

Minor version	Description
2.25.9	New features Optimized the performance of consistent reads in low-concurrency scenarios. Bug fixes Fixed an issue where persistent connections experienced unexpected transient disconnections due to the hybrid transactional and analytical processing (HTAP) feature.
2.25.8	New features Added support for automatic request distribution among row store and column store nodes for HTAP. Bug fixes Fixed an issue where replaying a failed read request to the primary node could cause a crash.
2.25.7	Bug fixes Fixed an issue where consistent reads could fail during high write concurrency.
2.25.5	New features Added support for transaction replay. This feature ensures persistent connections for in-progress transactions during a switchover. Bug fixes Fixed an issue where new connections could be blocked when the primary MySQL node was quickly restarted in place after a crash. Fixed an issue where changing proxy parameters or nodes could cause uneven load balancing for some persistent connections.
2.25.4	New features Added support for a load balancing routing policy based on the number of active requests. For more information, see Load balancing algorithms. Added support for configuring the primary node as a fallback node for the read-only proxy.
2.25.3	Bug fixes Fixed an issue that caused occasional errors when establishing connections with transaction-level connection pooling.
2.25.2	New features Added support for the consistent read feature for MySQL 5.6. Bug fixes Fixed an issue where a `SELECT for UPDATE` statement failed if a column name was the keyword `disable`. Fixed an issue where sessions were unexpectedly disconnected due to wait_timeout.
2.25.1	New features Added support for setting the read consistency level for read/write splitting.
2.24.3	Bug fixes Fixed an issue where a SELECT FOR UPDATE statement failed if a column name was the keyword disable. Fixed an issue where sessions were unexpectedly disconnected due to wait_timeout. Fixed a schema error caused by the transaction-level connection pool when adding a read-only node.
2.24.1	Bug fixes Fixed an out-of-memory (OOM) issue caused by an excessively large recv-q for backend connections. Fixed an issue where the schema was incorrectly reused by the transaction-level connection pool when adding a node.
2.9.5	New features Added support for setting the minimum number of reserved instances. Bug fixes Fixed an issue where the bandwidth of a single connection was limited under high network latency. Fixed an issue where load balancing could become uneven after a failed node recovered.
2.9.3	Bug fixes Fixed an issue where load balancing could become uneven for some persistent connection scenarios in read/write splitting mode. Fixed a memory leak issue caused by the SHOW WHERE statement, which was introduced in version 2.9.1.
2.9.1	New features Added support for configuring a connection pool and latency threshold for read-only endpoints. Added support for persistent connections during passive switchovers. Optimized persistent connections to support transactions that have no write operations under the Read Committed (RC) isolation level. Bug fixes Fixed a `thread id already exists` error caused by thread ID rotation. Thread IDs are now less likely to rotate. Fixed an issue where a `Kill Query` operation on a read-only address was not broadcast, which could prevent the request from being `Kill`ed.
2.8.41	New features Upgraded the kernel to community version 2.3.15. Note Make sure that the minor engine version of your RDS for MySQL instance is 20240131 or later. To upgrade the version, see Upgrade the minor engine version.
1.14.8/1.14.9	Bug fixes Fixed an issue where a Kill statement could cause a session to hang. Fixed an issue where sessions on a read-only node with a weight of 0 could not be killed. Fixed an issue where the bandwidth of a single connection was limited under high network latency. Fixed an issue where load balancing could become uneven after a failed node recovered. Fixed an issue where a hung MHD thread caused task stream failures. Fixed a memory leak that occurred when the system processed short-lived connections. Fixed an issue where the force_node syntax did not take effect.
1.14.7	New features Added a performance monitoring metric for the number of persistent connection failures. Bug fixes Fixed a Java Database Connectivity (JDBC) error that occurred during an upgrade from MySQL 5.7 to 8.0. Fixed an issue where locking a MySQL 5.6 instance could cause connection authentication to fail for the cluster. Fixed an issue where the proxy protocol failed after a quick restart of a crashed MySQL 5.7 instance. Fixed an issue where requests could fail during database and table recovery.
1.14.6	New features Added the persistent connection feature for active switchover scenarios.
1.14.5	Bug fixes Added compatibility with the session tracker of MySQL 8.0.33. This fixes an issue where client connections could be dropped after the connection pool feature was enabled.
1.14.3/1.14.4	Bug fixes Fixed an issue where the dual-write protection feature incorrectly identified the primary node, making the proxy endpoint unavailable. Added an error code for the dual-write protection feature. When this feature is triggered, the client receives a corresponding error. Fixed an issue where proxy endpoint authentication failed if the account host was in CIDR format. Fixed an issue where the first read statement in a transaction was forwarded to a read-only node when transaction splitting was disabled.
1.14.1/1.14.2	New features Added a dual-write protection feature to prevent data write errors caused by a dual-primary scenario during an abnormal switchover. If this feature is enabled and multiple primary nodes exist, the proxy endpoint becomes unavailable.
1.13.42	Bug fixes Fixed an issue where connection establishment failed due to an excessive number of database connections. Fixed an issue where an internal scheduled task caused response time (RT) jitter.
1.13.41	Performance optimizations Optimized the performance of the database proxy in scenarios with many failed authentication attempts. Optimized the identity verification feature. When an incorrect identity verification occurs, throttling is changed from global granularity to account-level granularity. Bug fixes Fixed an issue where the transaction resolution was lost during transaction splitting. Fixed an issue where environment variables were not reset in the transaction-level connection pool. Fixed an issue where a prepared statement failed to close in a distributed transaction (XA transaction). Fixed several internal exceptions.
1.13.33	New features Added support for the MySQL utf8mb3 encoding format. Bug fixes Fixed an issue where a SELECT FOR UPDATE statement was incorrectly routed due to an excessive number of parameters in a prepared statement.
1.13.27	Performance optimizations Optimized the proxy parsing performance for INSERT statements. Bug fixes Fixed some Secure Sockets Layer (SSL) compatibility issues with clients.
1.13.25	Bug fixes Fixed a memory leak caused by authentication failures. Fixed an issue where the proxy could unexpectedly crash in multi-Endpoint scenarios.
1.13.22	New features Added support for using the `SELECT LAST_INSERT_ID()` statement to obtain the unique ID of a sharded table after an INSERT operation. Added support for the FOUND_ROWS() function. Added support for routing COM_STATISTICS to read-only instances. Optimized the transaction-level connection pool. Added support for routing GEO functions to read-only instances. Added some internal monitoring metrics. Bug fixes Connections are no longer sent to locked instances in RDS. Fixed routing errors caused by incorrect parsing of some statements. Fixed an issue where stmt_exec failed in some scenarios. Fixed an issue where the `load data infile` statement failed to execute.
1.13.17	Bug fixes Fixed some internal faults.
1.13.5	New features Added support for routing all requests to a specified node (Force Node Connection). Example: `/force_proxy_internal/set force_node = 'pi-123';`. This routes all subsequent requests on the connection to the specified node pi-123. Note If the specified node is abnormal, the error `set force node 'pi-123' is not found, please check.` is returned. Added support for routing a single request to a specified node (Force Node Query). Example: `/force_node='pi-123'/ show processlist;`. This routes the request to the specified node pi-123. Note If the specified node is abnormal, the error `'force hint server node is not found, please check'.` is returned. Added some internal monitoring metrics. Bug fixes Fixed an issue where requests were routed to a read-only instance if the statement contained the MODE keyword. Fixed an issue that caused uneven load balancing under certain conditions.
1.12.10	New features Added support for SSL encryption for dedicated proxy connection addresses. Bug fixes Fixed an issue where establishing an SSL connection failed for MySQL 8.0. Fixed an issue where the dedicated proxy failed to route new requests to a node after the node recovered from an abnormal state to a normal state.
1.12.7	New features Added support for the `show full processlist` syntax. Added support for the XA transaction syntax. Bug fixes Fixed an error with the `show processlist` statement for MySQL 8.0. Fixed several issues with the transaction-level connection pool. Fixed several issues that caused connection establishment to fail.
1.11.12	New features Added support for transaction-level connection pooling. Bug fixes Optimized load balancing for persistent connections. New requests on existing persistent connections can be routed to a node after it recovers from an abnormal state. Optimized the Prepare syntax to support Prepare unicast. Fixed a connection failure that occurred when a MySQL 5.7 client connected to a MySQL 5.6 database with Deprecate EOF enabled. Fixed an issue where the connection was dropped when the database was changed within a stored procedure. Fixed an issue where the client reported a `Packets out of order` error if a single row in a result set with large messages exceeded 16 MB. Fixed an issue where transactions opened on a read-only instance using `set autocommit=0` were not closed promptly. Fixed an issue where `lock in shared mode` statements were routed to a read-only instance. Fixed an issue where `select handler from abc for update` statements were routed to a read-only instance. Fixed an authentication failure for a single user with multiple hosts.
1.10.7	Bug fixes Fixed several issues with the session-level connection pool.
1.9.23	New features Added support for root account connections. Added support for SSL-VPN connections. Bug fixes Fixed an issue where `change user` failed. Fixed an issue where `load file` failed. Fixed an issue where the application reported an `Exception: Packets out of order` error because the client received an incorrect sequence message. Fixed an issue where connections to read-only instances were dropped when the primary instance was abnormal.
1.9.14	New features Supports hint syntax: `/FORCE_SLAVE/, /FORCE_MASTER/`. Bug fixes Fixed an issue that caused garbled characters because the default charset value was incorrect. Fixed an issue where an incorrect string was returned for the MySQL version number.

References

Related API operations

API operation	Description
DescribeDBProxy	Queries the details of a database proxy.