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".
MySQL Router is now included in MySQL Server's source and monolithic binary packages. The MySQL Router standalone packages continue to exist, as before.
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 https://download.opensuse.org/repositories/devel:/gcc/SLE-12/devel:gcc.repo ... shell> zypper install ./mysql-router-community-8.0.*rpm
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
ttlconfiguration 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 #28292073)
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)
--directoryto 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 (mysql_innodb_cluster_metadata.schema_version) compatibility check is now checked at runtime, when before it only happened during the bootstrap process. (Bug #28147601)
--userset 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 #27577694)