Release Notes for MariaDB MaxScale 6.2.4
MariaDB MaxScale is an advanced database proxy, firewall, and query router.
MariaDB MaxScale 6.2.4 was released on 2022-03-30. This release is of General Availability (GA) maturity.
Many internal MaxScale threads have been named, so that they can be easily differentiated during profiling and debugging. (MXS-3997)
When a client tries to connect to MaxScale using TLS ciphers that are unsupported or disabled on the MaxScale node, MaxScale will write more detailed error messages to the MaxScale error log. (MXS-3665)
Starting with this release, the following error message can be written to the MaxScale error log:
error : (34) SSL operation failed for Client DCB at 'CLIENT_IP': error:1417A0C1:SSL routines:tls_post_process_client_hello:no shared cipher (Client ciphers: CLIENT_CIPHER_LIST) (Our ciphers: MXS_CIPHER_LIST)
Client cipherssection is only logged when the MaxScale node uses OpenSSL 1.1.1 or later.
maxctrl create reportcommand is executed, MaxScale generates a report describing the state of all MaxScale objects in JSON format and saves the output to a file. The report can be helpful in issue diagnosis and troubleshooting.
Can Result in Unexpected Behavior
When the Cache Filter (
cache) is used and an uncacheable statement is executed as part of a multi-statement query (such as
SELECT * FROM tab1 WHERE ..; SELECT * FROM tab2 WHERE ..), the statement's results can be improperly cached. (MXS-4053)
Starting with this release, the Cache Filter will not cache any results for multi-statement queries.
Starting with this release, the Cache Filter's error handling has improved, and its log messages have been clarified.
In previous releases, the following error message could be written to the MaxScale error log:
error : [storage_redis] Expected status message in the context of queued command, but received a ARRAY.
In the MaxGUI, the Query Editor does not clear the query history. (MXS-4061)
Starting with this release, the Query Editor will clear the query history after 30 days.
When a Listener is configured to listen on all available network addresses (such as
0.0.0.0with IPv4 or
::with IPv6), the MaxGUI Query Editor uses the wrong address to connect to the Listener. (MXS-4058)
Starting with this release, when a Listener is configured to listen on all available network addresses, the MaxGUI Query Editor will connect to the Listener using the IPv4 loopback address (
In previous releases, attempting to connect to the Listener could cause the following error message to be raised:
Connection to [::]:9999 failed. Error 2002: Can't connect to server on '::' (113)
In MaxGUI, the Query Editor truncates the column names in the header row in "Data Preview" display. (MXS-4018)
Starting with this release, column names will not be truncated in "Data Preview".
Starting with this release, the error message will only be written to the MaxScale error log once.
In previous releases, the following error could be repeatedly written to the MaxScale error log:
error : [MONITOR] Could not query events of 'SERVER': Query 'SELECT Event_schema, Event_name FROM information_schema.EVENTS WHERE Status = 'ENABLED';' failed: 'Cannot proceed, because event scheduler is disabled'. Event handling can be disabled by setting 'handle_events' to false.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 6.2.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_
SUSE Linux Enterprise Server 12 (x86_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 18.04 (x86_
Ubuntu 20.04 (x86_