Dear MySQL users, MySQL Router 8.0.14 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.14. 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.14, see the "Generally Available (GA) Releases" tab at http://dev.mysql.com/downloads/router. Package binaries are available for several platforms and also as a source code download. Documentation for MySQL Router can be found at http://dev.mysql.com/doc/mysql-router/en/ Enjoy! Changes in MySQL Router 8.0.14 (Not yet released) * Functionality Added or Changed * Bugs Fixed Functionality Added or Changed * A new dynamic configuration bootstrap feature was added that tracks the current MySQL InnoDB cluster Metadata servers. This replaces the existing bootstrap_server_addresses option with the new dynamic_config option in mysqlrouter.conf. MySQL Router now tracks and stores active MySQL InnoDB cluster Metadata server addresses and loads them if Router is restarted. Previously, metadata server information was defined during Router's initial bootstrap operation and stored statically as bootstrap_server_addresses in the configuration file. This new dynamic_config option is generated by --bootstrap and is defined under mysqlrouter.conf's [DEFAULT] section. Its value points to a generated JSON file named state.json that's initialized with InnoDB cluster Metadata server addresses and the group replication ID; and additional information is added and updated while Router is running. The bootstrap process no longer defines bootstrap_server_addresses because dynamic_config replaces its functionality; and these two options cannot be set at the same time. For backwards compatibility, if only bootstrap_server_addresses is set then it functions as it did in previous Router versions and this new dynamic configuration functionality is not used. (Bug #28082857, Bug #91029) * MySQL Router now persistently tracks the metadata server addresses rather than only using the static list defined in the configuration file using the destinations option. Bugs Fixed * The --version output was aligned with MySQL Server's layout. (Bug #28899194) * Linking Router against libmsyqlclient that was built with DBUG enabled led to slow Router shutdown procedures. (Bug #28656618) * Fixed a thread shutdown race condition. (Bug #28610484) * Sending mysqlrouter a SIGTERM would take at least 100ms to shut down. Now a concurrent plugin shutdown queue was added to speed up the shutdown process. (Bug #28570122) * A metadata-cache API method was added to check the initialization status. Routing plugins use this during initialization to safely register the callbacks after metadata-cache is initialized. (Bug #28569717) * Installing MySQL Server with Router from source or building a tarball with "make package" would create a top level "data/" directory as part of the "Router" component. Due to possible collisions with MySQL Server, "data/" was changed to "var/lib/mysqlrouter". (Bug #28537733) * The connection error counter that blocks clients after max_connect_errors connection errors did not reset after a successful connection. (Bug #27995042, Bug #90809) -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql
