tencent cloud

PrevNext

Feedback

search by keyword

Recent Pages

Documentation
TencentDB for MySQL
    Documentation
    Download PDF

    Database Proxy Kernel Release Notes

    Last updated: 2024-11-14 15:51:17
    Download PDF
    This document describes the kernel version updates of the TencentDB for MySQL database proxy.
    Note:
    If the MySQL kernel version requirements are not met, you can upgrade the kernel version of your database first as instructed in Upgrading Kernel Minor Version.
    Database Proxy Version
    MySQL Kernel Version Requirements
    Description
    1.4.2
    MySQL 5.7 20211230 and later MySQL 8.0 20221215 and later
    Fixes
    Fixed the issue of excessive memory usage after the transaction-level connection pool is enabled.
    1.4.1
    MySQL 5.7 20211230 and later
    MySQL 8.0 20221215 and later
    Feature updates
    Supports the transaction-level connection pool feature.
    Fixes
    Fixed the issue that DDL statements would get stuck in the secondary database.
    1.3.14
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Feature updates
    The statements SHOW BINLOG EVENTS and SHOW BINARY LOGS are now routed to the root instance.
    Optimized the issue that querying large messages may result in excessive memory consumption.
    Fixes
    Fixed the occasional inconsistency between the character set sorting of the handshake messages and the backend databases.
    Fixed the issue that the primary-secondary switch in the primary database may cause interruption in the read-only address connection.
    Fixed the issue of the potential authentication failure when a specified IP address matches multiple accounts simultaneously.
    1.3.13
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Feature updates
    Now, system variables related to select binlog will be executed in the primary database.
    Added new high-availability detection statements to reduce the migration caused by false fault detections.
    Optimized the memory usage of the database proxy kernel in multi-threading scenarios.
    Fixes
    Fixed the issue that executing the prepare statement in a read-only transaction would result in an error.
    Fixed the performance issue caused by frequent connection establishment with an incorrect username.
    After transaction splitting is enabled, commit and rollback statements will be routed to all nodes to prevent pending uncommitted transactions on RO nodes.
    1.3.12
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Feature updates
    Now system variables will be read in the primary database.
    Fixes
    Fixed the issue that a large number of connections triggering momentary disconnection prevention could cause some connections to be stuck for too long.
    Fixed the issue that a large number of connections triggering re-load balancing could cause some connections to fail to be broken as expected.
    1.3.11
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that too many accounts could lead to connection failures.
    Note:
    Version 1.3.12 already includes this fix, so it is recommended to upgrade to 1.3.12 directly.
    1.3.10
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that encountering specific messages during message processing could cause anomalies.
    1.3.9
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that annotations in multi-statements caused incorrect parsing.
    1.3.8
    MySQL 5.7 20211030 and later MySQL 8.0 20211202 and later
    Feature updates
    Supports more functions updated in MySQL 5.7 and 8.0.
    Optimized the parser cache to reduce OOM probability under a large number of complex SQL statements.
    Added traffic monitoring metrics for the database proxy.
    Supports the dynamic CLB feature.
    Fixes
    Fixed the issue that the momentary disconnection prevention feature might fail for some connections under a high connection count.
    1.3.7
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Fixes
    Fixed the routing error of the `select for update` statement in some cases.
    Modified the `select @@read_only` statement and made it possible to be routed to the source database. This prevents some frameworks that use read_only flags from misjudging the database proxy as unwritable.
    Fixed the database proxy node exceptions caused by a database instance HA in some scenarios.
    1.3.4
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that the 'show processlist' command returned incomplete data.
    1.3.3
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that an error was reported when the session connection pool reused connections to send `change_user` to the backend, and the issue that the PREPARE statement was not correctly handled by the database proxy after a new connection was established.
    1.3.2
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Fixes
    Fixed the issue that `execute` statement didn't have a parameter type
    1.3.1
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Feature updates
    Allowed instances with a weight of 0 to sustain read requests when the weight of all valid instances under the database proxy is 0.
    Supported the multi-AZ deployment architecture where read-only instances can be mounted across AZs.
    Provided the read-only mode.
    Supported transaction split.
    Supported momentary disconnection prevention, i.e., connection persistence, where the client will not be disconnected when a database instance HA switch occurs because of a scheduled task.
    1.2.1
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Feature updates
    Supported the `db lower_case_table_names` parameter, indicating not to verify the letter case by default.
    Supported returning error messages in the query stage when errors occur during database proxy connection establishment.
    1.1.3
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211202 and later
    Feature updates
    Supported the use of hint routing information in the `COM_PREPARE` message preprocessed by MySQL. After hint is used in `PREPARE` to specify the routing target, subsequent `execute` messages will be sent to the specified backend node.
    Fixes
    Fixed the issue that the frontend connection was reset immediately after source-replica switch of the source instance on the database proxy was performed.
    Fixed the issue that load balancing might fail when read-only instances exceeded the latency threshold. Routing will resume normally when the read-only instance latency falls below the threshold.
    Fixed the issue that MySQL 8.0 might return incorrect handshake information and cause connection failures.
    1.1.2
    MySQL 5.7 20211030 and later
    MySQL 8.0 20211130 and later
    Feature updates
    Supported MySQL 8.0.
    Supported the connection pool feature at the connection level, which is useful in scenarios where non-persistent connections to the database are frequently established. The database proxy will save connections and reuse them during subsequent connection establishments.
    Supported the reconnection feature for read-only instances. In persistent connection scenarios, when a read-only instance is restarted or added, the database proxy will automatically establish a connection and restore routing to it.
    Updated the internal memory management mechanism to reduce the memory usage.
    Fixes
    Fixed the issue that the client connection persisted after the backend connection was closed due to timeout.
    Fixed the issue that the internal cache might cause excessively rapid increase of the memory utilization.
    Fixed the occasional issue that messages in an incorrect format were returned.
    1.0.1
    MySQL 5.7 20201230 and later
    Feature updates
    Supported MySQL 5.7.
    Supported read/write separation.
    Supported read weight assignment in read/write separation.
    Supported the configuration of source-replica replication delay threshold. Routing to a read-only instance will be stopped if its delay exceeds the thresholds and will be recovered after it drops below the threshold. If the source-replica replication is interrupted, disconnected read-only instances will be removed directly.
    Supported the configuration of the least number of read-only instances. When read-only instances are removed, if the number is set to N, at least N instance(s) will be retained for routing.
    Supported the failover configuration, which is enabled by default. If it is disabled and the read weight of the source instance is 0, after all read-only instances are removed, an error will be reported for read requests. If failover is enabled and the read weight of the source instance is not 0, requests will be routed to the source instance.
    Supported using the HINT syntax to specify routing nodes.
    Contact Us

    Contact our sales team or business advisors to help your business.

    Contact Us
    Technical Support

    Open a ticket if you're looking for further assistance. Our Ticket is 7x24 avaliable.

    Submit a Ticket
    7x24 Phone Support
    Copyright © 2013-2024 Tencent Cloud. All Rights Reserved.
    Privacy PolicyLegalCookie Policy