Documentation Home
MySQL Router Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 163.7Kb
PDF (A4) - 163.3Kb

MySQL Router Release Notes  /  Changes in MySQL Router 8.0.35 (2023-10-25, General Availability)

Changes in MySQL Router 8.0.35 (2023-10-25, General Availability)

Deprecation and Removal Notes

  • The allow_primary_reads parameter of the destinations URI is now deprecated and subject to removal in a future version of MySQL Router. Use the PRIMARY_AND_SECONDARY parameter instead. For example:


    (WL #15871)

  • Metadata Schema v1.x support is now deprecated and subject to removal in a future version of MySQL Router. Connecting to a Cluster which uses this version now triggers a warning stating that the metadata version is deprecated and the Cluster metadata should be upgraded. (WL #15876)

Functionality Added or Changed

  • MySQL Router now recognizes accounts with empty password sent from PHP over the classic MySQL protocol. (Bug #35463338)

Bugs Fixed

  • Queries larger than 16MB were not properly handled if Connection Sharing was enabled. (Bug #35769702)

  • Unclosed comments, /* without a corresponding closing /*, caused MySQL Router to close unexpectedly if Connection Sharing was enabled. (Bug #35769610)

  • Authentication failed for third-party clients using non-SSL connections, with caching-sha2-password and the following SSL options configured:

    • client_ssl_mode set to PREFERRED or PASSTHROUGH

    • server_ssl_mode=AS_CLIENT

    An error similar to the following was returned:

            Couldn't read RSA public key from server

    (Bug #35737521)

  • MySQL Router closed unexpectedly when attempting to connect to a ClusterSet but only had access to members without quorum. (Bug #35705590)

  • If the directory used for bootstrapping contained a symlink, the keyring's master key could not be located. An error similar to the following was returned:

      Error: Master key for keyring at '/bootstrapPath/data/keyring' 
      could not be read

    (Bug #35630329)

  • Under certain circumstances, MySQL Router did not shutdown when closed with SIGTERM or SIGINT. It was possible for a connection to be in an intermediate state and block the shutdown until that remaining connection was closed by the user. (Bug #35574557)

  • If an invalid client greeting was received, the following message was logged:

            loop(): Input too short

    This message was not helpful to the user. As of this release, an error message is returned to the client and no error message is logged if the packet is invalid. (Bug #35523018)

  • MySQL Router maintained the router-server connection until the transaction was complete, even when the client-router connection had closed. This could result in a max-connection error.

    As of this release, MySQL Router checks the client-router connection status while waiting for the transaction response. (Bug #35515899)

  • Routing on named sockets did not resume after Cluster recovery. Error 2002 was logged. (Bug #35503286)

  • MySQL Router error log did not contain MySQL Router version information. (Bug #35503191)

  • MySQL Router did not reject ambiguous port configuration. For example, if both bind_address and bind_port were specified with different port numbers. (Bug #34972789)

  • Under certain circumstances, on Microsoft Windows platforms, it was not possible to run MySQL Router as a service. An error message stating the MySQL Router configuration file could not be found was logged even though the configuration file was present and correct. (Bug #33301070)