2.2 KiB
MariaDB MaxScale 2.1.1 Release Notes
Release 2.1.1 is a Beta release.
This document describes the changes in release 2.1.1, when compared to release 2.1.0.
For any problems you encounter, please consider submitting a bug report at Jira.
Dropped Features
MaxAdmin
The following deprecated commands have been removed:
enable log [debug|trace|message]disable log [debug|trace|message]enable sessionlog [debug|trace|message]disable sessionlog [debug|trace|message]
The following commands have been deprecated:
enable sessionlog-priority <session-id> [debug|info|notice|warning]disable sessionlog-priority <session-id> [debug|info|notice|warning]
The commands can be issued, but have no effect.
New Features
Failover Recovery for MySQL Monitor
The failover_recovery option allows the failed nodes to rejoin the cluster
after a failover has been triggered. This makes it possible for external actors
to recover the failed nodes without having to manually clear the maintenance
mode.
For more information about the failover mode and how it works, read the MySQL Monitor documentation.
Bug fixes
Here is a list of bugs fixed since the release of MaxScale 2.1.0.
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 X.Y.Z. Further, master always refers to the latest released non-beta version.
The source code is available here.