The Ultimate Guide to High Availability with MariaDB
This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-22. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB MaxScale 22.08.12 Release Notes -- 2024-03-11

MariaDB MaxScale 22.08.12 Release Notes -- 2024-03-11

Release 22.08.12 is a GA release.

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

External CVEs resolved.

New Features

  • MXS-4862 ssl_version should specify minimum version

Bug fixes

  • MXS-5007 Top-level service reconnection may cause a use-after-free
  • MXS-5000 insertstream uses an error code from the reserved client range
  • MXS-4998 MaxScale may send two COM_QUIT packets
  • MXS-4997 MaxScale: BUILD/install_build_deps.sh: deprecated --force-yes
  • MXS-4996 Order of servers is different after restart if runtime modifications have been done
  • MXS-4995 The "static" property of an object is lost upon restart
  • MXS-4994 Multiple warnings from the REST-API are printed on the same line
  • MXS-4981 Hang on shutdown when large batches of session command are pending
  • MXS-4979 COM_CHANGE_USER may leave stale IDs to be checked
  • MXS-4978 Read-only transactions are incorrectly tracked
  • MXS-4968 REST-API TLS certificates can be reloaded but the path to them cannot be altered
  • MXS-4967 Log throttling is sometimes disabled too early
  • MXS-4956 Session commands ignore delayed_retry_timeout
  • MXS-4947 Tables in information_schema are treated as a normal tables
  • MXS-4945 GUI doesn't validate object name uniqueness accurately
  • MXS-4943 delayed_retry timeout errors do not have enough information
  • MXS-4934 Use-after-free after service deletion
  • MXS-4930 'maxctrl reload tls' has the usage of 'maxctrl reload service'
  • MXS-4926 History length of sessions is not visible in the REST-API
  • MXS-4925 self link in /maxscale/logs/data is off by one page
  • MXS-4924 Very fast client and server may end up busy-looping a worker
  • MXS-4922 Memory growth for long-running sessions that use COM_CHANGE_USER
  • MXS-4921 Memory growth for long-running sessions that use prepared statements
  • MXS-4912 Query classifier cache total-size book-keeping may be wrong
  • MXS-4910 readconnroute performance regression in 6.4
  • MXS-4908 Undefined behavior with module commands that take no arguments
  • MXS-4907 Nested parameters in PATCH /v1/maxscale/ do not work correctly
  • MXS-4906 MonitorWorker::call_run_one_tick() called more often than intended
  • MXS-4903 Bad configuration in PATCH may partially configure monitors
  • MXS-4900 maxctrl show qc_cache can easily overwhelm MaxScale
  • MXS-4896 Reducing the size of the query classifier cache does not cause excess entries to be freed.
  • MXS-4888 Unable to type custom row limit in the Query configuration dialog
  • MXS-4879 Transaction state viewed from the session is different from the transaction state as viewed from RWS.
  • MXS-4865 5.5.5- prefix should not be added if all backends are MariaDB 11

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.

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.