
In some cases you might want to use a specific address/interface when connecting to a server instead of the default one. With the global parameter 'local_address' it can now be specified which address to use.
2.8 KiB
MariaDB MaxScale 2.1.14 Release Notes
Release 2.1.14 is a GA release.
This document describes the changes in release 2.1.14, when compared to release 2.1.13.
If you are upgrading from release 2.0, please also read the following release notes:
For any problems you encounter, please consider submitting a bug report at Jira.
New Features
Local Address
It is now possible to specify what local address MaxScale should use when connecting to servers. Please refer to the documentation for details.
Bug fixes
Here is a list of bugs fixed in MaxScale 2.1.14.
- MXS-1627 MySQLAuth loads users that use authentication plugins
- MXS-1620 CentOS package symbols are stripped
- MXS-1602 cannot connect to maxinfo with python client
- MXS-1601 maxinfo crash at execute query 'flush;'
- MXS-1600 maxscale it seen to not coop well with lower-case-table-names=1 on cnf
- MXS-1576 Maxscale crashes when starting if .avro and .avsc files are present
- MXS-1543 Avrorouter doesn't detect MIXED or STATEMENT format replication
- MXS-1416 maxscale should not try to do anything when started with --config-check
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.