MariaDB MaxScale 2.4.9 Release Notes -- 2020-04-30

MariaDB MaxScale 2.4.9 Release Notes -- 2020-04-30

Release 2.4.9 is a GA release.

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

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

New Features

  • MXS-2861 Allow TLS cipher selection between Maxscale and client

Bug fixes

  • MXS-2972 USE sent to wrong server
  • MXS-2969 maxscale service still not stopped / restarted on package upgrade
  • MXS-2968 Avrorouter direct replication sets wrong server_id
  • MXS-2956 admin_ssl_ca_cert reads the wrong certificate
  • MXS-2954 cluster sync doesn't update global configuration options
  • MXS-2948 Fix cluster sync
  • MXS-2943 csmon doesn't work with pluggable ColumnStore
  • MXS-2942 DELETE of a monitor doesn't check whether it uses servers
  • MXS-2939 Session commands do not trigger reconnection
  • MXS-2931 MXS-2810 still unfixed in RHEL / CentOS 6 packages

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.