MariaDB MaxScale 6.2.2 Release Notes -- 2022-02-14

MariaDB MaxScale 6.2.2 Release Notes -- 2022-02-14

Release 6.2.2 is a GA release.

This document describes the changes in release 6.2.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-3989 Rebalancing may cause MaxScale to crash
  • MXS-3978 Binlog router appends -BinlogRouter to master version string again and again ...
  • MXS-3973 Session capabilities are not frozen on session startup
  • MXS-3966 MariaDBMonitor does not log connection error on startup
  • MXS-3959 Transaction replay doesn't reset transaction on implicit commit
  • MXS-3958 MaxScale stalls and crashes occasionally
  • MXS-3955 Crash after unexpected result
  • MXS-3953 Transaction start written to binlog prematurely
  • MXS-3949 "transaction" is always parsed as a reserved word
  • MXS-3948 Toggle query result columns isn't working as expected
  • MXS-3932 Xpand monitor doesn't show full configuration in diagnostic output
  • MXS-3886 Hang in RoutingWorker::execute_concurrently semaphore.hh:146
  • MXS-3865 Shutdown bug

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.

Packaging

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

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.