Changes in MySQL Router 8.0.37 (2024-04-30, General Availability)

Bugs Fixed

• If a hostname was not resolved, due to a DNS failure, MySQL Router did not check if that host became available again, later. (Bug #36246652)

• MySQL Router's bootstrap process checks the mysql.user table for the unsupported mysql_native_password authentication plugin. If the bootstrap user had no access to the table, the following error was returned:

          Failed checking the Router account authentication plugin: Error executing MySQL query "select host, plugin from mysql.user where user = 
          'user'": SELECT command denied to user 'user'@'host' 
          for table 'user' (1142)

  As of this release, this error is not returned. (Bug #36225456)

• The following error was displayed if MySQL Router was closed before the metadata cache started:

          Error: routing:_: Metadata Cache not initialized

  (Bug #36151125)

• If an incoming port is opened and closed by a TCP connection, such as a load balancer or a service-monitoring utility performing a health check, the connection counts towards the limit defined by max_connect_errors, even though the connection was not established. This could lead to MySQL Router closing the incoming port when the error limit is reached.

  As of this release, max_connect_errors is not incremented if the Router's incoming port is opened and closed without establishing a connection. (Bug #36104070)

• The following error did not provide enough information for troubleshooting:

          timestamp routing ERROR [code] connecting to backend  failed: Connection timed out (generic:110)

  As of this release, it contains the following details:

  • Route name and client source.

  • resolve() errors.

  • Hostname, IP addresses, and errors for each connection attempt.

  • The amount of time spent on the connection attempt.

  (Bug #35503245)