MaxScale 21.06 MariaDB MaxScale 6.2.4 Release Notes -- 2022-03-30

You are viewing an old version of this article. View the current version here.

MariaDB MaxScale 6.2.4 Release Notes -- 2022-03-30

Release 6.2.4 is a GA release.

This document describes the changes in release 6.2.4, 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.

New Features

  • MXS-3997 Name threads for better CPU usage view
  • MXS-3665 Provide more feedback on TLS cipher mismatch

Bug fixes

  • MXS-4061 Query Editor: Query history isn't cleared after passing the retention period
  • MXS-4058 Query Editor: Connection to [::]:9999 failed. Error 2002: Can't connect to server on '::' (113)
  • MXS-4053 The cache does not handle multi-statements properly.
  • MXS-4045 Add maxctrl command for dumping the whole REST API output
  • MXS-4043 Creating a listener in the GUI requires defining the service twice
  • MXS-4040 Mariadbmon constantly logs errors if event scheduler is disabled
  • MXS-4018 Query Editor: Column names should be auto adjust in the Data Preview
  • MXS-3936 Expected status message in the context of queued command, but received a ARRAY

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.