Dear MySQL users,

MySQL Router 8.0.13 is a new release for MySQL Router 8.0 series.

MySQL Router 8.0 is highly recommended for use with MySQL Server 8.0 and 5.7.
Please upgrade to MySQL Router 8.0.13.

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.

To download MySQL Router 8.0.13, see the "Generally Available (GA)
Releases" tab at Package
binaries are available for several platforms and also as a source code

Documentation for MySQL Router can be found at



Changes in MySQL Router 8.0.13 (2018-10-22)

     * Functionality Added or Changed

     * Bugs Fixed

Functionality Added or Changed

     * To align package names with MySQL Server, the community
       package name prefix changed from "mysql-router-" to
       "mysql-router-community-". This change also allows
       upgrading from MySQL Router 2.1 to 8.0. Additionally, a
       "mysql-router" meta package was added that redirects
       "mysql-router" to "mysql-router-community".

Bugs Fixed

     * For SLES 12, MySQL binary distributions are now built
       using GCC 7. The lowest supported GCC version on this
       platform is now 5.3 (previously 4.8.5).
       Installing MySQL Router 8.0.13 or higher RPM packages on
       SLES 12 platforms requires that the GCC Devel repo is
       enabled, for example:
shell> cd /etc/zypp/repos.d/
shell> wget
shell> zypper install ./mysql-router-community-8.0.*rpm

       (Bug #28685857)
       References: See also: Bug #92147.

     * The log level was changed from INFO to DEBUG for the
       InnoDB cluster Metadata server and replicaset
       connections. Because MySQL Router's ttl configuration
       option defaults to 0.1, these each generate 10 log
       entries per second. (Bug #28424243)

     * Running MySQL Router against an invalid InnoDB cluster
       would report internal SQL errors, such as "Unknown
       database 'mysql_innodb_cluster_metadata'", rather than
       user-friendly information that the cluster is not set up
       as a metadata server. The generated error now clarifies
       the reason and points to related documentation. (Bug

     * The --version output was aligned across all binaries to
       include license related text. (Bug #28262453)

     * On Windows, starting Router after uninstalling the Router
       service would cause Router to hang as it assumed the
       service was still enabled. (Bug #28261217)

     * Passing in --directory to an unwritable empty directory
       would yield a generic error. (Bug #28228800)

     * The error code ER_CON_COUNT_ERROR is now used instead of
       HY000 ("unknown") when the maximum number of allowed
       connections is exceeded. (Bug #28183810)

     * The metadata version
       compatibility check is now checked at runtime, when
       before it only happened during the bootstrap process.
       (Bug #28147601)

     * Bootstraping with --user set to the same user running the
       bootstrap operation would halt with a "setegid failed"
       error. (Bug #27698052)

     * An error related to running out of available threads was
       only logged once until Router was restarted. (Bug

     * MySQL Router is now included in MySQL Server's source and
       monolithic binary packages. The MySQL Router standalone
       packages continue to exist, as before.

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to