Database Proxy Version | Release Date | MySQL Kernel Version Requirement | Description |
1.3.21 | April 2026 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates Multiple kernel monitoring metrics have been added, including statistics for Prepare and Execute calls. Improved the stability of the momentary disconnection prevention capability under high-concurrency traffic. Added support for MySQL 8.4. Issue Fixes Fixed the issue where the momentary disconnection prevention feature might cause process crashes under extreme scenarios. Fixed the memory management logic related to the momentary disconnection prevention feature and optimized the memory leak issue of the feature. |
1.3.20 | November 2025 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue where connections might not be restored with a low probability after momentary disconnection prevention is enabled. |
1.3.19 | July 2025 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue that the momentary disconnection prevention feature might cause incorrect connection character sets. |
1.3.17 | May 2025 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue of errors that sometimes occurred when a read-only transaction was enabled after the transaction split feature was enabled. Fixed the issue of character set errors that might occur during connection reuse after the connection pool was enabled. |
1.3.16 | March 2025 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue where errors might occur with a low probability when precompiled statements are executed under a read-only address. Fixed the issue where abnormal Capabilities Flags might occur after the connection pool is enabled. Fixed the issue that the connection might be interrupted when the replication delay of a read-only instance changed frequently after delayed read-only instance removal was enabled. |
1.3.15 | December 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Performance optimization Optimized memory usage under high loads and resolved the issue where memory might remain at a high level for an extended period. Issue Fixes Fixed the issue where momentary disconnection prevention might fail with a certain probability. |
1.3.14 | November 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates The SHOW BINLOG EVENTS and SHOW BINARY LOGS statements are now routed to the primary instance. Optimized the issue where excessive memory usage might occur when queries return large packets. Issue Fixes Fixed the issue where the character set collation in the handshake packet occasionally did not match that of the backend database. Fixed the issue where connections to the read-only address might be interrupted during primary/secondary switching on the primary database. Fixed the issue where authentication might fail when an IP address specified for an account matches multiple accounts. |
1.3.13 | 24-Aug | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates Now, system variables related to SELECT binlog are sent to the primary database for execution. Added new high-availability probe statements to reduce migrations caused by false positive failures. Optimized the memory usage of the database proxy kernel in multi-threaded scenarios. Issue Fixes Fixed the issue that an error was reported when a precompiled statement was executed in a read-only transaction. Fixed the performance issue that occurred when connections were frequently established using an incorrect username. Fixed the issue that uncommitted transactions existed on read-only nodes because COMMIT and ROLLBACK statements were routed to all nodes after transaction split was enabled. |
1.3.12 | June 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates The SHOW VARIABLES statement will be sent to the primary database for execution. Issue Fixes Fixed the issue where, when a large number of connections trigger momentary disconnection prevention, some connections might become stuck for an excessively long time. Fixed the issue where, when a large number of connections triggered CLB rebalancing, some connections were not disconnected as expected. |
1.3.11 | May 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue where an excessive number of accounts could cause connection establishment to fail. Note: Version 1.3.12 already includes the fix for this issue. It is recommended to upgrade directly to version 1.3.12. |
1.3.10 | March 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue where an exception might occur when response packets containing specific messages are processed. |
1.3.9 | January 2024 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue where multi-statement blocks containing comments could not be parsed correctly. |
1.3.8 | September 2023 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates Added support for more functions introduced in newer versions of MySQL 5.7 and 8.0. Optimized the parser cache to reduce the probability of OOM when a large number of complex SQL statements are processed. Added traffic monitoring metrics for database proxies. Added support for the dynamic CLB feature. Issue Fixes Fixed the issue where, under a large number of connections, the momentary disconnection prevention feature might fail to work for some connections. |
1.3.7 | April 2023 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue of route errors that occurred when the SELECT...FOR UPDATE statement was executed in some cases. The SELECT @@read_only statement will be routed to the primary database to avoid using the read_only tag under certain frameworks, preventing the system to mistakenly determine that the database proxy is unwritable. Fixed the issue that the database proxy node was switched due to database instance errors in some scenarios. |
1.3.5 | January 2023 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Performance optimization Optimized the performance when a large number of read statements were executed concurrently. |
1.3.4 | December 2022 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue that the returned data of SHOW PROCESSLIST was incomplete. |
1.3.3 | November 2022 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue that an error may occur during statement precompilation under a session-level connection pool. |
1.3.2 | October 2022 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Issue Fixes Fixed the issue that an error may occur during statement precompilation. |
1.3.1 | October 2022 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates When the weights of all valid instances under a database proxy are set to 0, read requests are also distributed to instances with a weight of 0. Supports a multi-AZ deployment architecture and allows mounting cross-AZ read-only instances. Provides a read-only mode. Supports transaction splitting. The feature supports momentary disconnection prevention, which maintains connections so that client connections are not interrupted during HA switches of database instances caused by scheduled tasks. |
1.2.1 | June 2022 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates Supported the lower_case_table_names parameter. By default, the case is not verified. |
1.1.3 | June 2021 | MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later | Feature updates Supported using a hint that indicates the route information in precompiled MySQL statements. When a hint is used in a PREPARE statement to specify the route destination, subsequent EXECUTE messages will be sent to the specified backend node. Issue Fixes Frontend connections are immediately reset after the primary instance on the database proxy performs a primary/secondary switch. Fixed the issue where CLB might fail after read-only instances exceeded the latency threshold. Now, routing is restored normally after the latency of read-only instances falls back within the threshold. Fixed the issue where MySQL 8.0 might return incorrect handshake information, causing connection establishment to fail. |
1.1.2 | June 2021 | MySQL 5.7 20211030 and later MySQL 8.0 20211130 and later | Feature updates Supports MySQL 8.0. The feature supports connection-level connection pools to address scenarios where frequent connections to the database are established in non-persistent connection services. The database proxy saves connections and reuses them for the next connection establishment. The feature supports reconnection for read-only instances. In persistent connection scenarios, when a read-only instance is restarted or a new read-only instance is added, the database proxy automatically re-establishes connections to the read-only instances to restore routing. The internal memory management mechanism has been updated, resulting in lower memory consumption in the new version. Issue Fixes Fixed the issue where client connections remained active after backend connections timed out and disconnected. Fixed the issue where internal caching could cause memory to grow too rapidly. Fixed the issue where malformed packets might be returned under rare circumstances. |
1.0.1 | February 2022 | MySQL 5.7 20201230 and later | Feature updates Supports MySQL 5.7. Supports read/write splitting. Supports read weight configuration in read/write splitting. Supports setting a primary-secondary replication latency threshold. When the latency of a read-only instance exceeds the threshold, it is removed from the routing. When the latency falls back below the threshold, routing is restored. If the primary-secondary replication is interrupted, the affected read-only instance is removed directly. Supports setting a minimum retention count. When read-only instances are removed, if a minimum retention count of n is configured, at least n read-only instances are retained in the routing. Supports failover configuration, which is enabled by default. If failover is disabled and the read weight of the primary instance is 0, read requests will return an error after all read-only instances are removed. If failover is enabled or the primary database weight is not 0, requests are routed to the primary instance. Supported using a hint to specify the destination node for routing. |
Database Proxy Version | Release Date | MySQL Kernel Version Requirement | Description |
1.47 | May 2026 | MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later Read-only analysis engine 2.2410.4.0 and later | Issue Fixes Fixed the issue where the momentary disconnection prevention or transaction-level connection pool feature could become abnormal when variables or database names used by the application contain special characters. Fixed the issue where the transaction-level connection pool did not correctly reset the sql_select_limit session variable when connections were reused, resulting in incomplete query result sets. Fixed the issue where instance memory leakage could occur when an application fails to execute a prepared Statement. Fixed the issue where database proxies might return an incorrect database version number during the handshake phase after a client connects. Fixed the issue of inaccurate statistics for number of transaction starts. Fixed the issue of untimely connection reclamation in the transaction-level connection pool under specific transaction scenarios. Fixed the issue where process crashes could occur due to concurrency contention during route changes. Fixed the issue where database proxies incorrectly parsed multi-statement queries sent by clients. Fixed the issue of thread blocking caused when database proxies obtain the LSN. Fixed the issue where the momentary disconnection prevention feature could cause process crashes under specific scenarios. |
1.4.5 | September 2025 | MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later Read-only analysis engine 2.2410.4.0 and later | Feature updates Supported the failover of LibraDB engine nodes to ordinary read-only nodes. Supported LibraDB engine nodes participating in read-write separation and load balancing as read-only nodes. Issue Fixes Fixed the issue of memory leakage that occurred with a low probability in the transaction-level connection pool. Fixed the issue of connection interruption that occasionally occurred during the primary database switch after the transaction-level connection pool is enabled. |
1.4.4 | March 2025 | MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later Read-only analysis engine 2.2410.4.0 and later | Feature updates It supports integrating instances of the read-only analysis engine LibraDB into the read-write separation of the database proxy and fault elimination. Supported using the hint /* to ap */ in SQL statements to route SQL statements to a read-only analysis engine instance. |
1.4.2 | August 2023 | MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later | Issue Fixes Fixed the issue of excessive memory usage after the transaction-level connection pool is enabled. |
1.4.1 | July 2023 | MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later | Feature updates Supports the transaction-level connection pool feature. Issue Fixes Fixed the issue where DDL statements could get stuck on the secondary database. |
Was this page helpful?
You can also Contact sales or Submit a Ticket for help.
Help us improve! Rate your documentation experience in 5 mins.
Feedback