Release Notes for MariaDB MaxScale 22.08.4
MariaDB MaxScale is an advanced database proxy and query router. MaxScale is a component of MariaDB database products.
MariaDB MaxScale 22.08.4 was released on 2023-01-19. This release is of General Availability (GA) maturity.
This document describes the changes in
MaxScale 22.08.4 when compared to
Can result in a hang or crash
When a worker's sessions are rebalanced, MaxScale can crash due to a race condition. (MXS-4423)
With a service-to-service configuration where one service uses another service as its target, MaxScale can crash due to a segmentation fault if a query is replayed right before the connection is closed. (MXS-4460)
After upgrading to MaxScale 22.08, MaxScale uses more memory, which can lead to an out-of-memory (OOM) condition. (MXS-4451)
When the MaxScale REST API is enabled, if the
admin_ssl_certparameter is configured to use a PEM file that contains a chain of certificates instead of a single certificate, MaxScale crashes when the first REST API request is made. (MXS-4442)
Can result in unexpected behavior
When a MaxScale listener performs a TLS handshake with a client, MaxScale does not provide the full certificate chain in the server hello message. (MXS-4450)
In previous releases, MaxScale only provides the MaxScale certificate in the server hello message.
Starting with this release, MaxScale provides the full certificate chain in the server hello message.
In previous releases, the following log messages could appear in the MaxScale log:
info : (10) [readwritesplit] (SERVICE_NAME); Master 'SERVER_NAME' failed: #HY000: Lost connection to backend server: network error (SERVER_NAME: 104, Connection reset by peer) error : (10) [readwritesplit] (SERVICE_NAME); Lost connection to the master server, closing session. Lost connection to master server while connection was idle. Connection has been idle for 120 seconds. Error caused by: #HY000: Lost connection to backend server: network error (SERVER_NAME: 104, Connection reset by peer). Last close reason: <none>. Last error:
In previous releases, if a table exists on more than one node, MaxScale routes queries to the first node with the table in its set, even if that node is unavailable.
Starting with this release, if a table exists on more than one node, MaxScale checks that a node is available before routing queries to it.
With Schema Router (
schemarouter), when the
USEstatement or the
COM_INIT_DBcommand are used to select a database and the database is located on multiple shards, the database is only selected on a single shard, and the selected database on the remaining shards is left unmodified. (MXS-4470)
With the Query Log All (QLA) Filter (
maxctrl rotate logsis executed and the
userparameter is defined for the filter, the logs are reopened for any sessions that do not match the user, which causes errors to be logged for each executed statement. (MXS-4435)
SET STATEMENTis used to set a variable's value for the lifetime of a statement, MaxScale's internal query classifier would classify the statement to be routed to all nodes instead of only to the node executing the statement. (MXS-4434)
In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 22.08.4 is provided for:
CentOS 7 (x86_
Debian 9 (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 18.04 (x86_
Ubuntu 20.04 (x86_
Ubuntu 22.04 (x86_