This topic describes the release notes of PolarProxy in PolarDB for MySQL.

Query the version number

Log on to the PolarDB console. Click the name of a cluster. Choose Settings and Management > Version Management. On the page that appears, check the PolarProxy version. PolarProxy version

Release notes for PolarProxy

Note The following list describes only the major versions of PolarProxy. The version of PolarProxy that you use may not be included in the list.
  • 2.4.22 (Release date: September 10, 2021)
    Category Description
    Fixed issues
    • PolarProxy fails to close PREPARE statements, which causes high memory usage in databases.
    • Persistent connections fail in specific scenarios.
    • An error occurs on PolarProxy when the default cluster endpoint is changed to a read-only endpoint.
    • PolarProxy does not respond in specific scenarios.
  • 2.4.18 (Release date: August 12, 2021)
    Category Description
    Fixed issues
    • If no character set is specified for a Java Database Connection (JDBC) application, the text of the application data is garbled when the database node connected to the application is restarted or when account authentication fails.
    • The database service fails to connect to Flink applications.
    • Some requests that are supposed to be routed to a temporary table are routed to other tables.
  • 2.4.17 (Release date: July 14, 2021)
    Category Description
    New features and performance optimization PolarDB for MySQL clusters that run MySQL 5.7 support persistent connections in failover scenarios.
    Fixed issues
    • The response time becomes longer because a MySQL database account fails to authenticate.
    • When a read-only node becomes faulty, the system continues routing new requests to the node.
    • Several internal metrics are added to monitor the cluster performance.
    • Read-only endpoints cannot be accessed if the parallel query feature is enabled.
    • A routing error occurs when you query the current timestamp.
    • A routing error occurs when the FOR UPDATE clause is parsed.
    • A routing error occurs due to incorrect syntax analysis of the @a keyword in a JOIN clause.
    • The attempt to log on to a MySQL 8.0 client fails to be verified because no password is provided.
    • Several PREPARE statements cannot be executed.
  • 2.4.12 (Release date: May 20, 2021)
    Category Description
    New features and performance optimization The dynamic data masking feature is supported. For more information, see Dynamic data masking.
    Fixed issues PolarProxy exceptions occur in specific scenarios.
  • 2.4.7 (Release date: March 15, 2021)
    Category Description
    New features and performance optimization The persistent connection feature is supported. For more information, see Persistent connections.
    Fixed issues A routing error occurs when you execute a statement in which LOCK IN SHARED MODE is specified.
  • 1.13.25 (Release date: August 18, 2021)
    Category Description
    Fixed issues
    • A memory leak occurs on PolarProxy when a MySQL database account fails to authenticate.
    • PolarProxy does not respond when multiple endpoints are used to access a cluster.
  • 1.13.22 (Release date: July 21, 2021)
    Category Description
    New features and performance optimization
    • The SELECT last_insert_id() statement can be executed after the transaction-level connection pool feature is enabled.
    • The FOUND_ROWS function is supported after the transaction-level connection pool feature is enabled.
    • The COM_STATISTICS command can be routed to read-only nodes.
    • The transaction-level connection pool feature is optimized.
    • The global consistency feature is optimized. Requests can be routed to a read-only node even if the node is the only read-only node that meets the consistency requirements.
    • Queries that contain geo functions can be routed to read-only nodes.
    • Several internal metrics are added to monitor the cluster performance.
    Fixed issues
    • Routing errors occur due to incorrect parsing of several SQL statements.
    • In specific scenarios, the stmt_exec() command fails to run after the stmt_long_data() command is run.
    • The LOAD DATA INFILE statement cannot be executed.
  • 1.13.5 (Release date: December 1, 2020)
    Category Description
    New features and performance optimization
    • Eventual consistency is applicable to transaction splitting.
    • The following hints are supported:
      • force node connection /*force_proxy_internal*/set force_node = 'pi-aaaaaaaaa';

        After you establish this connection, all requests are routed only to the node pi-aaaaaaaaa. If the node becomes faulty, the set force node 'pi-aaaaaaaaa' is not found, please check. error message is returned.

      • force node query /*force_node='pi-aaaaaaaa'*/ show processlist;

        This statement can be executed only on the node pi-aaaaaaaa. If the node becomes faulty, the 'force hint server node is not found, please check.' error message is returned.

    Fixed issues
    • If the mode keyword is included in the SELECT type, status, mode, WHERE gtx_id = '4' FOR UPDATE; statement, the statement is routed to read-only nodes.
    • In specific scenarios, loads are unbalanced among database nodes in a cluster.
    • The stmt_close command fails to run after a PREPARE statement is executed.
    • Several internal metrics are added to monitor the cluster performance.
  • 1.12.10 (Release date: October 19, 2020)
    Category Description
    Fixed issues
    • PolarDB clusters that run MySQL 8.0 cannot be accessed after SSL encryption is enabled for the clusters.
    • After the state of a database node changes from DOWN to RUNNING, PolarProxy fails to route subsequent requests to the database node.
  • 1.12.7 (Release date: August 6, 2020)
    Category Description
    New features and performance optimization
    • The SHOW FULL PROCESSLIST statement is supported.
    • XA transactions are supported.
    Fixed issues
    • Several issues of the transaction-level connection pool are fixed.
    • Several issues that occur when you access read-only nodes in a global database network (GDN) are fixed.
    • An error occurs when you execute the SHOW PROCESSLIST statement on a cluster that runs MySQL 8.0.
    • Several connections failed.
  • 1.11.12 (Release date: June 22, 2020)
    Category Description
    New features and performance optimization
    • The transaction-level connection pool feature is supported.
    • The parallel query feature is supported for read-only endpoints of PolarDB for MySQL clusters that run MySQL 8.0.
  • 1.10.7 (Release date: March 18, 2020)
    Category Description
    New features and performance optimization The global consistency feature is supported.
    Fixed issues An error occurs when you initialize system environment variables for a session-level connection pool.
  • 1.9.23 (Release date: February 21, 2020)
    Category Description
    New features and performance optimization
    • The root account can be used to connect to a cluster.
    • SSL encryption is supported.
    Fixed issues
    • The change user command fails.
    • The load file command fails.
    • When an application receives packets that are not organized in a valid sequence, the application returns the Exception: Packets out of order error message.
    • Read-only endpoints are disconnected when the primary node becomes faulty.
  • 1.9.14 (Release date: December 24, 2019)
    Category Description
    New features and performance optimization
    • The /*FORCE_SLAVE*/ and /*FORCE_MASTE*/ hints are supported.
    • You can configure whether to offload read requests from the primary node to read-only nodes.
    Fixed issues
    • Garbled text exists in the response if the default value of the charset parameter is invalid.
    • The returned string that indicates the MySQL engine version is incorrect.

Update the version

If the PolarProxy of your cluster is not of the latest version, you can update the version based on your business requirements. For more information, see Upgrade the version.
Note Version updates can resolve specific issues that occur on your PolarProxy version. If the issue you encountered still exists after you update PolarProxy, we recommend that you submit a ticket to contact technical support.