MySQL Router 2.1.4 GA has been released

[Sreedhar S]

Dear MySQL users,

MySQL Router 2.1.4 GA is the second GA release for MySQL Router 2.1.

The MySQL Router is a new building block for high availability
solutions based on MySQL InnoDB clusters.

By taking advantage of the new Group Replication technology,
and combined with the MySQL Shell, InnoDB clusters provide an
integrated solution for high availability and scalability for
InnoDB based MySQL databases, that does not require advanced MySQL
expertise.

The deployment of applications with high availability requirements
is greatly simplified by MySQL Router. MySQL client connections are
transparently routed to online members of a InnoDB cluster, with
MySQL server outages and cluster reconfigurations being automatically
handled by the Router.

MySQL Router 2.1 also introduces the following additions:

* Automatic setup/bootstrap with a MySQL InnoDB cluster
* Support for the new X protocol
* Support for deployments inside self-contained directories
* Easy and secure password management using a built-in keyring

You can download MySQL Router from http://dev.mysql.com/downloads/router.
Package binaries are available for several platforms and also as a
source code download.

If you are a commercial customer, MySQL Router is available via the
MySQL Oracle Support (MOS) website. Packages will be available on
eDelivery at the next monthly refresh.

Documentation for MySQL Router can be found at
http://dev.mysql.com/doc/mysql-router/en

Enjoy!

Changes in MySQL Router 2.1.4 (2017-07-21)

   Functionality Added or Changed

     * Added support for the validate_password plugin when using
       the STRONG setting. (Bug #25858394)

     * Added support to bootstrap the router using Unix sockets.
       (Bug #25450756)

     * Added support to bootstrap the router using IPv6
       addresses. (Bug #25225260, Bug #25828663)

   Bugs Fixed

     * Bootstrapping a MySQL Router instance did not work when
       DNS lookups were unsuccessful on the host where the
       bootstrap operation was performed. (Bug #26100966)

     * After a primary failure within an InnoDB cluster, MySQL
       Router required an extended amount of time to reconnect.
       (Bug #26044181, Bug #86259)

     * An incorrect profile setting produced permission-denied
       errors during MySQL Router bootstrap operations when
       AppArmor was enabled. (Bug #26041542)

     * Stand-alone routing failed and produced errors when used
       with a valid URI. (Bug #25973199)

     * The bootstrap procedure for the system-wide bootstrap now
       creates the proper directory ownership required to start
       the router, when before it failed to start in some cases.
       (Bug #25956532, Bug #86050)

     * Difficulties observed when installing and starting MySQL
       Router on older Windows platforms due to missing
       libraries are now resolved. (Bug #25853059, Bug
       #25494942)

     * Passing in a directory to the --config option instead of
       a MySQL Router configuration file now reports a more
       relevant error, when before it did not mention that a
       file is required. (Bug #25800863)

     * Sample MySQL Router configuration files were generated
       with the .ini extension instead of with the .conf file
       extension as expected. (Bug #25616924)

     * Specifying an invalid user account in the metadata_cache
       section of the MySQL Router configuration file after
       bootstrapping now issues an appropriate error message.
       (Bug #25460958)

     * Omitting a MySQL Router configuration file when using the
       --config option now displays an error indicating an empty
       path instead of throwing an exception. (Bug #25449685)

     * The commercial version of MySQL Router did not have the
       correct setting for the AppArmor profile configuration
       file /etc/apparmor.d/usr.sbin.mysqlrouter. (Bug
       #25253001, Bug #84074)

     * Invalid configuration variables in the MySQL Router
       configuration file that expect numeric values, such as
       the expiration time (TTL), now report errors. (Bug
       #24756621)

On Behalf of the MySQL/ORACLE RE Team,
-Sreedhar S