Release Notes for MariaDB MaxScale 6.4.1
MariaDB MaxScale is an advanced database proxy, firewall, and query router.
MariaDB MaxScale 6.4.1 was released on 2022-07-14. This release is of General Availability (GA) maturity.
The following example shows what the message can look like:
Reverse name resolution of address 'IP_ADDRESS' of incoming client 'USERNAME' took DURATION seconds. The resolution was performed to check against host pattern 'HOST_PATTERN', and can be prevented either by removing the user account or by enabling 'skip_name_resolve'.
If the warning frequently appears in the log, enabling the
skip_name_resolveparameter can help improve performance.
Starting with this release, when the value of the
priorityparameter is negative, the Galera Monitor (
galeramon) will eliminate the node from the
Masterselection process. When the value is
0, the Galera Monitor (
galeramon) will still select the node as
Masterwhen no other nodes were available.
Can Result in Crashes, Hangs, Stalls
Can Result in Unexpected Behavior
When MaxScale's REST API is configured to use HTTPS, cookies do not include the
Path=/option, but the omission does not cause problems. (MXS-4193)
maxctrl call commandis executed and errors occur, the output with the error message is not displayed, but the output could be included in the next command that causes an error to occur. (MXS-4177)
Some read-only parameters could be modified at runtime. (MXS-4171)
maxctrl create monitoris executed, if some of the servers specified by the
--serversoption are already monitored and others are unmonitored, the monitor can still be partially created and associated with the unmonitored servers, even though the operation fails. (MXS-4170)
In earlier releases, Xpand Monitor (
xpandmon) could only dynamically detect nodes based on their IP address, so a bootstrap node was required to be defined using its IP address.
Starting with this release, Xpand Monitor (
xpandmon) performs a DNS lookup to convert hostnames to IP addresses, so a bootstrap node can be defined using its hostname.
The internal query classifier can classify some non-multi-statement queries as multi-statement queries. This can affect how the query is routed in some cases. (MXS-4180)
When TLS is enabled, MaxScale tries to generate 512-bit RSA keys, which are disabled when OpenSSL is running in FIPS mode. (MXS-4181)
In earlier releases, when this issue occurred on a system using OpenSSL 1.0.1 (such as some older CentOS 7 and RHEL 7 releases), the following error messages would be written to the MaxScale log:
error : (SERVER_NAME); 512-bit RSA key generation failed. error : (SERVER_NAME); Unable to initialize SSL for server 'SERVER_NAME' error : Failed to create a new server.
In earlier releases, when the
max_slave_replication_lagparameter was set to a non-zero value with Galera Monitor (
galeramon), the following error message would be written to the MaxScale log when Read/Write Split Router (
readwritesplit) tried to route a query to a replica node:
Could not find valid server for target type TARGET_SLAVE (COM_QUERY: QUERY_TEXT), closing connection.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 6.4.1 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_
Rocky Linux 8 (x86_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 18.04 (x86_
Ubuntu 20.04 (x86_
Ubuntu 22.04 (x86_