MariaDB MaxScale 2.0.3 Release Notes

MariaDB MaxScale 2.0.3 Release Notes

Release 2.0.3 is a GA release.

This document describes the changes in release 2.0.3, when compared to release 2.0.2.

If you are upgrading from release 1.4.4, please also read the release notes of release 2.0.0, release 2.0.1 and release 2.0.2.

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

Updated Features

MXS-1027 Add Upstart support (including respawn) for MaxScale

MaxScale now provides an Upstart configuration file for systems that do not support systemd.

Bug fixes

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

  • MXS-1048: ShemaRouter can't handle backquoted database names
  • MXS-1047: Batch inserts through Maxscale with C/J stall
  • MXS-1045: Defunct processes after maxscale have executed script during failover
  • MXS-1044: Init-Script for SLES 11 displays error messages when called
  • MXS-1043: Reading last insert id from @@identity variable does not work with maxscale
  • MXS-1033: maxscale crushes on maxadmin request
  • MXS-1026: Crash with NullAuth authenticator
  • MXS-1009: maxinfo sigsegv in spinlock_release
  • MXS-964: Fatal: MaxScale 2.0.1 received fatal signal 6
  • MXS-956: Maxscale crash: Removing DCB 0x7fbf94016760 but was in state DCB_STATE_DISCONNECTED which is not legal for a call to dcb_close

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


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.