The Ultimate Guide to High Availability with MariaDB
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.6 Release Notes -- 2020-12-15

MariaDB MaxScale 2.5.6 Release Notes -- 2020-12-15

Release 2.5.6 is a GA release.

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

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

NOTE After the release of 2.5.6 it was noticed that configuring the same server for both the persistent pool (configuration settings persistpoolmax and persistmaxtime) and the proxy protocol (configuration setting proxy_protocol) may in some situations lead to a crash. Using either one is ok. We will release 2.5.7 with a fix for this as soon as possible (January 2021).

New Features

Bug fixes

  • MXS-3338 Last statement in read-only transaction doesn't trigger transaction replay
  • MXS-3335 MaxScale 2.5.6 and Xpand Direct connection issue with xpandmon
  • MXS-3334 Master failure triggers replay of read-only transaction
  • MXS-3333 Malformed error messages
  • MXS-3328 Persistent Connections on Maxscale 2.5 seem to break client authentication
  • MXS-3327 Memcachd/Redis cache storage must be disabled if memcached/redis not reachable
  • MXS-3326 Host class does not accept all valid domain names.
  • MXS-3325 Redis cache storage does not accept dashes in server names.
  • MXS-3316 Redis cache storage must be disabled if Redis not connectible
  • MXS-3313 MaxScale cache must use timeout when connecting to redis/memcached
  • MXS-3312 MaxScale not allowing login and sometimes crashes when cache server not available
  • MXS-3311 routed_packets not updated by readconnroute
  • MXS-3307 Multiple binlogrouters in the same MaxScale
  • MXS-3301 MaxScale does not recognize xpand properly
  • MXS-3295 Layout of classify REST API endpoint stores non-parameter data in parameters object
  • MXS-3293 Backticks not stripped in USE statements.
  • MXS-3292 Unable to execute use database
  • MXS-3283 Scramble should be composed of characters
  • MXS-3282 Select query inside transactions are routed to slave with session_track_trx_state=true
  • MXS-3272 maxctrl not prompt directy for the password
  • MXS-3271 dump_last_statements=on_close doesn't log session ID
  • MXS-3270 MaxScale 2.5.5 crashes with signal 11
  • MXS-3264 The event mechanism is not configured.
  • MXS-3256 Match pinloki initial setup to that of MariaDB server
  • MXS-3251 Hang on shutdown when executing KILL query
  • MXS-3248 "error : (1672) Unexpected result state" with connection_keepalive
  • MXS-3199 KafkaCDC read stream data too slow
  • MXS-3172 Database grants with escape characters do not work (strip_db_esc)

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.