The Ultimate Guide to High Availability with MariaDB

MariaDB MaxScale 1.4.2 Release Notes

You are viewing an old version of this article. View the current version here.

MariaDB MaxScale 1.4.2 Release Notes

Release 1.4.2 is a GA release.

This document describes the changes in release 1.4.2, when compared to release 1.4.1.

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

Bug fixes

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

  • MXS-684: Password field still used with MySQL 5.7
  • MXS-683: qc_mysqlembedded reports as-name instead of original-name.
  • MXS-681: Loading service users error
  • MXS-680: qc_mysqlembedded fails to look into function when reporting affected fields
  • MXS-679: qc_mysqlembedded excludes some fields, when reporting affected fields
  • MXS-662: No Listener on different IPs but same port since 1.4.0
  • MXS-661: Log fills with 'Length (0) is 0 or query string allocation failed'
  • MXS-656: after upgrade from 1.3 to 1.4, selecting master isn't working as expected
  • MXS-616: Duplicated binlog event under heavy load.

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.

Comments

Comments loading...
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.