MaxScale 21.06 MariaDB MaxScale 6.1.2 Release Notes -- 2021-09-27

MariaDB MaxScale 6.1.2 Release Notes -- 2021-09-27

Release 6.1.2 is a GA release.

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

If you are upgrading from an older major version of MaxScale, please read the upgrading document for this MaxScale version.

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

Bug fixes

  • MXS-3775 Hang in RoutingWorker::execute_concurrently
  • MXS-3774 Maxscale crash during xpand scale up
  • MXS-3773 nosqlprotocol should report 0 as the minimum wire protocol version
  • MXS-3767 connector_plugindir does not pick up the default location.
  • MXS-3766 Not able to insert data on Masking enabled table
  • MXS-3759 Client hangs forever when server failed or restarted
  • MXS-3757 Don't allow any SIMD code run until called
  • MXS-3754 maxscale-6.1.1-1.rhel.8.x86_64 crashes and coredumps on first startup after upgrade maxscale-2.5.15-1.rhel.8.x86_64
  • MXS-3750 6.1.1 CentOS7 x86_64 RPMs fail on older CPUs without avx2 extension
  • MXS-3704 MaxScale always advertises the SESSION_TRACK capability even with servers that don't support it (XPand)
  • MXS-3580 Avrorouter should store full GTID coordinates

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