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


MySQL Router Release Notes  /  Changes in MySQL Router 8.0.36 (2024-01-16, General Availability)

Changes in MySQL Router 8.0.36 (2024-01-16, General Availability)

Bugs Fixed

  • It was not possible to build MySQL Router on 32-bit Linux platforms. (Bug #36040942)

  • If MySQL Router was bootstrapped over an existing configuration, the existing user's credentials were retrieved from the keyring and reused, even if the user used the deprecated authentication plugin, mysql_native_password.

    As of this release, MySQL Router checks the user's authentication method and, if it is set to mysql_native_password, changes it to the Cluster's default if there are no other user@host entries for the MySQL Router user. If there is more than one such entry, a warning is returned, advising the user to manually correct the authentication configuration. (Bug #35943415)

  • If MySQL Router was bootstrapped against an InnoDB Cluster, without using an existing account or using the --force-password-verification parameter, the auto-created metadata user was created using the mysql_native_password plugin. This plugin was deprecated in MySQL Server 8.1 and is subject to removal in a future release.

    As of this release, the metadata user is created using the default authorization plugin defined on the InnoDB Cluster. (Bug #35737357)

  • It was not possible to connect to MySQL Router with PHP and an account with an empty password using a command similar to the following:

    php -r 'mysqli_real_connect(mysqli_init(), "127.0.0.1", "empty", "");'

    Authentication failed with the following error:

    PHP Warning:  mysqli_real_connect(): Premature end of data
    (mysqlnd_wireprotocol.c:703) in Command line code on line 1
    PHP Warning:  mysqli_real_connect(): AUTH_RESPONSE packet 1 bytes
    shorter than expected in Command line code on line 1

    (Bug #35493871)

  • If a client aborted a TLS handshake due to a certificate which cannnot be verified, the following was incorrectly logged as an ERROR by MySQL Router:

       ERROR ... classic::loop() processor failed:
       error:0A000418:SSL routines::tlsv1 alert unknown ca
       (tls_err:167773208)

    As of this release, the connection is closed without a processor failed error and an INFO message is logged explaining why the TLS handshake failed. (Bug #35443773)

  • MySQL Router disconnected all connections to a Cluster if the user added a new instance to an existing Cluster with only one remaining member. This occurred because the new instance was present in the Group Replication metadata but not yet in the Cluster's metadata. MySQL Router assumed there was no quorum and disconnected. It was possible to reconnect after the new instance was represented in the Cluster's metadata.

    As of this release, MySQL Router relies only on the Group Replication metadata for quorum reporting. (Bug #33989165)