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


MySQL Router Release Notes  /  Changes in Release 2.1  /  Changes in MySQL Router 2.1.2 (2017-03-06, Release Candidate)

Changes in MySQL Router 2.1.2 (2017-03-06, Release Candidate)

Functionality Added or Changed

Bugs Fixed

  • After starting a Router instance, starting a second Router instance using the same configuration file as the first, would cause the second Router instance to exit due to bind_port conflicts. (Bug #25493968)

  • While bootstrapping router, the process to discover local interfaces had a memory leak. (Bug #25456674)

  • Fixed "use of uninitialized bytes" issues as discovered by valgrind. (Bug #25455825)

  • Bootstrapping did not throw errors when passing an empty string to any of the following options: tls-version, ssl-cipher, ssl-ca, ssl-capath, ssl-crl, ssl-crlpath succeeds, without throwing an proper error. In addition, ssl-mode VERIFY_CA would continue without requiring ssl-ca. (Bug #25436768)

  • After bootstrapping router with the --conf-use-sockets and --directory options, the socket path configuration value defined in the generated configuration file was invalid. This was because it used the socketsdir value in the socket path, but the directory was not created as part of the bootstrap process or when router was started. (Bug #25391460)

  • With SSL disabled on MySQL instances in a MySQL InnoDB cluster, passing in --ssl-mode REQUIRED along with a --tls-version version did not exit and emit an error. This now stops the bootstrap process and reports an error about requiring SSL. (Bug #25390144)

  • On Windows, immediately starting a bootstrapped Router installation would fail to load the generated configuration file.

    In addition, the generated text for missing configuration files was improved to also include the paths that were checked. (Bug #25343904)

  • On Windows, --bootstrap would not function if Router was compiled from source due to unresolved underlying paths. (Bug #25039423)

  • On Windows, --bootstrap failed to function without also passing in --directory. (Bug #25038772)

  • Bootstrapping with --config would overwrite an existing configuration file without warning. Now, if the generated configuration file is different, a backup file is created with the .bak file extension. (Bug #24763468)

  • Fixed memory leaks that were observed while bootstrapping with metadata cache configured. (Bug #24733015)

  • Improved group replication related error text. (Bug #24703342)