MariaDB MaxScale 2.4.11 Release Notes -- 2020-07-15

MariaDB MaxScale 2.4.11 Release Notes -- 2020-07-15

Release 2.4.11 is a GA release.

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

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

Bug fixes

  • MXS-3069 Unnecessary AuthSwitchRequest with old clients
  • MXS-3064 User loading query can run into charset collation problems
  • MXS-3059 Crash in Galera monitor
  • MXS-3057 session_trace enables all log levels
  • MXS-3055 DCB write errors with abstracted services
  • MXS-3054 Crash with persistent connections, schemarouter and local services abstracted as servers
  • MXS-3041 QC bug with keyword handler
  • MXS-3038 readwritesplit router should not open new connections to slaves lagging for more than max_slave_replication_lag seconds
  • MXS-3020 Parts of 2.4 manual still suggest to use deprecated maxadmin
  • MXS-2996 Query Type of 'SELECT ... LOCK IN SHARE MODE;'
  • MXS-2585 MaxScale dies with fatal signal 11
  • MXS-2584 Race condition between startup/shutdown and signal delivery
  • MXS-619 creating many short sessions in parallel leads to errors

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

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.