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


MySQL Router Release Notes  /  Changes in Release 8.0  /  Changes in MySQL Router 8.0.28 (2022-01-18, General Availability)

Changes in MySQL Router 8.0.28 (2022-01-18, General Availability)

Functionality Added or Changed

  • Added the --conf-set-option command line option to set a value for any generated configuration option during bootstrap. For example, setting --conf-set-option=logger.level=debug sets [logger]level=debug in the generated mysqlrouter.conf.

  • On Windows, the following options now accept a custom service name parameter: --install-service, --install-service-manually, and --remove-service. The previous and default value for each of these is MySQLRouter.

  • Added the ability to alter configuration options at runtime via the command line. The format is --section[:section_key].option_name=option_value; such as --DEFAULT.plugin_folder=/home/dev/. This new feature does not modify the configuration file as it only affects the runtime; and it overrides defaults and configured options.

Bugs Fixed

  • On Windows, removed the openssl/*.h includes to allow tls_context.h to include them in the correct order. This allows Router to build on Windows with OpenSSL 1.0.x. (Bug #33579528, Bug #105535)

  • Two informative text files were added: INFO_BIN contains information about the build environment used to produce the distribution, and INFO_SRC provides information about the product version and the source repository from which the distribution was produced. (Bug #33510726)

  • Fixed error reporting related to metadata-cache's role definition for its destination URL. Rather than report "Invalid server role in metadata cache routing" it's now more specific and references the allowed role values, which are PRIMARY, SECONDARY, and PRIMARY_AND_SECONDARY. (Bug #33444102)

  • With logging_folder set, Router would always output "logging facility initialized, switching logging to loggers specified in configuration" to the console; now this message is only displayed if previous console output was detected. (Bug #33327741)

  • Router could continue using a former Primary Cluster for periodic metadata updates despite it being an invalidated target_cluster. (Bug #33300235)

  • Router incorrectly accepted non-numeric values for numeric options. For example, 'a' was interpreted as '0'. They are now rejected. (Bug #32248283)