MariaDB MaxScale 2.4.1 Release Notes -- 2019-08-20

MariaDB MaxScale 2.4.1 Release Notes -- 2019-08-20

Release 2.4.1 is a GA release.

This document describes the changes in release 2.4.1, when compared to the previous release in the same series.

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

Bug fixes

  • MXS-2633 Pam authentication doesn't work with server 10.4
  • MXS-2603 MaxScale causes connections to break in Percona PXC Cluster
  • MXS-2598 memory leak on handling COM_CHANGE_USER
  • MXS-2597 MaxScale doesn't handle errors from microhttpd
  • MXS-2594 Enabling use_priority for not set priority on server level triggers an election
  • MXS-2578 Maxscale RPM issue PCI Compliancy
  • MXS-2577 Avrorouter direct conversion is not documented
  • MXS-2574 maxctrl alter user doesn't work on current user
  • MXS-2544 PAMAuth doesn't check role permissions
  • MXS-2521 COM_STMT_EXECUTE maybe return empty result
  • MXS-2446 Fatal on Maxscale server on reimaging clustrix setup being monitored.

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.


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

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. Further, the default branch is always the latest GA version of MaxScale.

The source code is available here.


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.