Release Notes for MariaDB MaxScale 6.4.8
MariaDB MaxScale is an advanced database proxy and query router.
MariaDB MaxScale 6.4.8 was released on 2023-07-31. This release is of General Availability (GA) maturity.
--load-alloption has been added to provide a way to show details about all supported MaxScale modules via REST API and/or MaxCtrl (MXS-4541)
Starting with this release, the option
--load-allcan be used with the
list modulescommand to show all supported MaxScale modules. When used without the
list modulescommand shows only the modules that are configured.
maxctrl list modules --load-all
Can result in a hang or crash
In previous releases, if a statement is split across multiple packets, the cache filter will forward the first packet and wait for a server response before sending the following ones, thus causing the session to hang.
Starting with this release, if a protocol command is split across multiple packets, the subsequent packets are sent forward without waiting for a response.
optimistic_trx=truecould result in excessive memory consumption and the process being killed by the OOM (out-of-memory) killer. (MXS-4656)
Starting with this release, when
optimistic_trxwill be disabled.
error : (SERVICE_NAME); Error received during replication from 'PRIMARY_HOST:PRIMARY_PORT': Could not open /var/lib/maxscale/binlogs//mariadb-bin.00000N for STOP_EVENT addition
Can result in unexpected behavior
When unsuccessfully starting a listener, a bad configuration could be persisted on disk. The error message generated by the unsuccessful start is misleading and incorrectly logged in the MaxScale log instead of being captured and sent to the REST API client. (MXS-4665)
Starting with this release, the following message is sent to the REST API client:
Listener 'NAME' was created but failed to start it.
404errors do not provide enough information about the cause of a problem. (MXS-4657)
Added a clarification to the MaxCtrl error message whenever an HTTP 404 response is given. Since the endpoints themselves should always be correct, the only thing that can go wrong is the object name or type.
The new error message is:
Check that the object exists and that it is of the correct type.
SSL setup between MaxScale and MariaDB Xpand is not working properly because the SSL parameters specified on the bootstrap server are not copied to the dynamic servers. (MXS-4683)
causal_reads=localis serialized as
causal_reads=truedue to the string and JSON conversion of the enumeration values preferring the legacy values. The enumeration serialization selects the first matching value from the list. (MXS-4666)
In previous releases, the legacy values are listed first, so the enumeration serialization prefers the legacy values.
Starting with this release, the new values are listed first, so the enumeration serialization prefers the new values.
Starting with this release, the binlog router index file is "for human information only". When the binlog router needs details about log files, it no longer reads the index file. Instead, the binlog router rereads log file names and update times from disk, and then recreates the index file.
In alignment to the MariaDB Engineering Policy, MariaDB MaxScale 6.4.8 is provided for:
CentOS 7 (x86_
Debian 10 (x86_
Debian 11 (x86_
Red Hat Enterprise Linux 7 (x86_
Red Hat Enterprise Linux 8 (x86_
Red Hat Enterprise Linux 9 (x86_
Rocky Linux 8 (x86_
Rocky Linux 9 (x86_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 20.04 (x86_
Ubuntu 22.04 (x86_