MariaDB MaxScale 2.3.6 Release Notes -- 2019-04-23

MariaDB MaxScale 2.3.6 Release Notes -- 2019-04-23

Release 2.3.6 is a GA release.

This document describes the changes in release 2.3.6, 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-2417 MaxScale main config should take precedence over runtime config on restart
  • MXS-2344 Support MASTER_SSL in mariadbmon for encrypting replication traffic

REST API & MaxCtrl: Hard maintenance mode

The new --force option for the set server command in MaxCtrl allows all connections to the server in question to be closed when it is set into maintenance mode. This causes idle connections to be closed immediately.

For more information, read the REST-API documentation for the set endpoint.

Bug fixes

  • MXS-2423 retain_last_statements not in maxctrl show maxscale
  • MXS-2419 Hangs on query during multiple transaction replays
  • MXS-2418 Crash on transaction replay if log_info is on and session starts with no master
  • MXS-2416 Possible memory leak
  • MXS-2324 Maxscale disconnect after commit without begin from Icinga2
  • MXS-2259 Maxscale consumes large amounts of memory even with buffer limits set.

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.