MariaDB MaxScale 2.1.6 Release Notes -- 2017-08-14

Release 2.1.6 is a GA release.

This document describes the changes in release 2.1.6, when compared to release 2.1.5.

If you are upgrading from release 2.0, please also read the following release notes: 2.1.5 2.1.4 2.1.3 2.1.2 2.1.1 2.1.0

For any problems you encounter, please consider submitting a bug report at Jira.

Bug fixes

Here is a list of bugs fixed in MaxScale 2.1.6.

• MXS-1352 Not all query failures in monitors are reported
• MXS-1351 Partially authenticated connections are put into the connection pool
• (MXS-1343)[https://jira.mariadb.org/browse/MXS-1343] MaxScale's binlogrouter does not send hostname to its master
• MXS-1338 Buffer objects are bound to indiviudual buffers

New Features

• It is now possible to configure the binlog router to identify itself to the master using a custom hostname: MXS-1343

Known Issues and Limitations

There are some limitations and known issues within this version of MaxScale. For more information, please refer to the Limitations document.

Packaging

RPM and Debian packages are provided for the Linux distributions supported by MariaDB Enterprise.

Packages can be downloaded here.

Source Code

The source code of MaxScale is tagged at GitHub with a tag, which is identical with the version of MaxScale. For instance, the tag of version X.Y.Z of MaxScale is maxscale-X.Y.Z.

The source code is available here.