This is a read-only copy of the MariaDB Knowledgebase generated on 2024-11-21. For the latest, interactive version please visit https://mariadb.com/kb/.

MariaDB MaxScale 2.5.29 Release Notes -- 2023-10-25

MariaDB MaxScale 2.5.29 Release Notes -- 2023-10-25

Release 2.5.29 is a GA release.

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

Bug fixes

  • MXS-4807 MaxScale does not always report the OS version correctly
  • MXS-4756 GUI caching issue
  • MXS-4749 log_throttling should be disabled if log_info is on
  • MXS-4747 log_throttling is hard to modify via MaxCtrl
  • MXS-4738 The fact that disable_master_failback does not work with root_node_as_master is not documented
  • MXS-4735 Connection IDs are missing from error messages
  • MXS-4724 slave_selection_criteria should accept lowercase version of the values
  • MXS-4717 information_schema is not invalidated as needed
  • MXS-4706 Cache does not invalidate when a table is ALTERed, DROPed or RENAMEd

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.

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.