MariaDB MaxScale 2.5.25 Release Notes -- 2023-03-30

MariaDB MaxScale 2.5.25 Release Notes -- 2023-03-30

Release 2.5.25 is a GA release.

This document describes the changes in release 2.5.25, 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-4566 RHEL8 Packages for 23.02.1 and 22.08.5
  • MXS-4557 Binlogrouter breaks if event size exceeds INT_MAX
  • MXS-4556 Maxscale ignores lower_case_table_names=1 on config file
  • MXS-4548 The statement canonicalizer cannot handle comments within statements
  • MXS-4524 Wrong server version assumption
  • MXS-4515 MaxScale leaks sessions if they are closed when writeq throttling is enabled
  • MXS-4514 skip_name_resolve is not modifiable at runtime
  • MXS-4510 Uncaught exception in binlogrouter
  • MXS-4504 IP wildcard values are not permitted in host values while using data masking
  • MXS-4494 Replication breaks if binlogfilter excludes events
  • MXS-4489 PHP program reports different collation_connection when connecting via Maxscale
  • MXS-4476 Memory leak in smartrouter
  • MXS-4474 MaxScale hangs with warning about "Worker 1 attempted to send a message to worker 1"
  • MXS-4473 Hang in smartrouter under heavy load
  • MXS-4469 Schemarouter routing logic documentation is out of date
  • MXS-4459 Improve match/exclude documentation for avrorouter and kafkacdc
  • MXS-4197 pinloki_start_stop is unstable
  • MXS-3972 The rpl_state in binlogrouter is not atomic

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