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

MaxScale 24.02 MariaDB MaxScale 24.02.3 Release Notes -- 2024-09-09

MariaDB MaxScale 24.02.3 Release Notes -- 2024-09-09

Release 24.02.3 is a GA release.

This document describes the changes in release 24.02.3, 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-5234 webpack warns about yargs
  • MXS-5232 Large batches of session commands may leave sessions alive for a long time
  • MXS-5231 Connections to servers in maintenance are sometimes not discarded
  • MXS-5227 MaxScale does not drop supplementary groups if --user is used
  • MXS-5226 LICENSE.TXT is a dangling symlink in RPMs
  • MXS-5213 Erroneous "Cluster gtid domain is unknown" error message during failover
  • MXS-5209 Reads with max_slave_connections=0 after a switchover do not discard stale connections
  • MXS-5206 Readwritesplit does not drop connections to severely lagging servers
  • MXS-5200 CMake 3.28.3 warnings
  • MXS-5198 Default logrotate config in .deb / docu missing params
  • MXS-5196 /maxscale/logs/data may return no data if maxlog=0 and syslog=1
  • MXS-5193 Multi-statement commands may end up being stored in the session command history
  • MXS-5191 Two cache filters in same service causes errors on session creation
  • MXS-5190 dotnet EntityFrameworkCore generates insert queries that are getting routed to all nodes as session write
  • MXS-5179 Active schema is not highlighted in the schema tree explorer
  • MXS-5171 MaxScale does not have time to open the file during rotation for a new binlog
  • MXS-5165 MariaDB Monitor rebuild server may try to chown "/var/lib/mysql/" instead of just "/var/lib/mysql"
  • MXS-5162 Post reboot binlog router entered stuck state
  • MXS-5160 postinst script prints output while installing
  • MXS-5159 MaxScale does not use remote address sent in proxy header from client for authenticating the client
  • MXS-5146 23.08.6 build ppc64le fails
  • MXS-5135 The GUI should clear all http readonly cookies
  • MXS-5133 Memory leak in namedserverfilter
  • MXS-5132 Inbound proxy protocol does not generate the correct error if proxy_protocol_network is not defined
  • MXS-5131 comment filter uses the wrong module name
  • MXS-5129 Cache may delete values from LRU but not from storage
  • MXS-5128 Failed patching passive parameter value
  • MXS-5127 DEALLOCATE PREPARE is not routed to all nodes
  • MXS-5126 Segfault in cache filter with default configuration
  • MXS-5125 Executing identical prepared statements may lose one of them on reconnection
  • MXS-5121 MaxScale detects wrong server character set
  • MXS-5109 A logout endpoint for the GUI to clear all http readonly cookies
  • MXS-4605 Monitor should drop the connection when faced with an Access Denied error

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.