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

MySQL Router Release Notes  /  Changes in Release 2.1  /  Changes in MySQL Router 2.1.3 (2017-04-12, General Availability)

Changes in MySQL Router 2.1.3 (2017-04-12, General Availability)

A known limitation of this release:


The --bootstrap command line option does not accept IPv6 addresses.

Functionality Added or Changed

  • Added functionality to also scan for Router configuration files with the .ini extension, to provide backward compatibility with previous Router installations.

    Router looks in the initial directory for the .conf version, then checks for a .ini version, and then repeats the process in the second directory that's typically the user's home directory. (Bug #25688333)

Bugs Fixed

  • On Linux, systemd based distributions defaulted to mysqlrouter.ini instead of mysqlrouter.conf. (Bug #25688333)

  • Bootstrapping as a super user (uid==0) without the --user option would generate files and directories that were owned by root an not accessible by others. Now, super users are required to pass in the --user option. Also while not recommended, the super user name can be passed in to force using the super user, such as --user=root. (Bug #25682736)

  • Router would compile against yaSSL but not OpenSSL. (Bug #25672823, Bug #85068)

  • On Solaris, MySQL Router would not start as it could not find the required (Bug #25638708)

  • On FreeBSD, a unit-test would always fail with "Bad Suki". (Bug #25549490)

  • Executing bootstrap with "ssl-mode VERIFY_CA" would not report an error when the corresponding certificate was not passed through ssl-ca. (Bug #25511157)

    References: See also: Bug #24732452.