The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-12-25. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB MaxScale 2.0.6 Release Notes -- 2017-06-14

MariaDB MaxScale 2.0.6 Release Notes -- 2017-06-14

Release 2.0.6 is a GA release.

This document describes the changes in release 2.0.6, when compared to release 2.0.5.

If you are upgrading from release 1.4, please also read the following release notes: 2.0.5, 2.0.4, 2.0.3, 2.0.2, 2.0.1 and 2.0.0.

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

Bug fixes

Here is a list of bugs fixed since the release of MaxScale 2.0.5.

  • MXS-1244: MySQL monitor "detect_replication_lag=true" doesn't work with "mysql51_replication=true"
  • MXS-1221: Nagios plugin scripts does not process -S option properly
  • MXS-1218: Use correct conversion specifier when printing 64-bit integers
  • MXS-1216: Fatal error while converting data
  • MXS-1191: Alter statement to a table with no create statement.
  • MXS-1180: cdc.py not producing anything with JSON format, but does with AVRO
  • MXS-1178: master_accept_reads doesn't work with detect_replication_lag

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 derived from 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.

Content reproduced on this site is the property of its respective owners, and this content is not reviewed in advance by MariaDB. The views, information and opinions expressed by this content do not necessarily represent those of MariaDB or any other party.