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.

Notable Changes

  • The priority parameter can now accept a negative value for a server, which eliminates the node from the Master selection process for Galera Monitor (galeramon). (MXS-4165)

  • If reverse name resolution takes longer than 1 second, a warning is now printed to the MaxScale log. (MXS-4148)

    • 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_resolve parameter can help improve performance.

Issues Fixed

Can result in a hang or crash

Can result in unexpected behavior

  • 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.
  • When maxctrl show filters is executed, the output does not contain filter diagnostics. (MXS-4166)

  • When the Cat Router (cat) is used, sessions are not always closed, which can trigger a debug assertion to fail. (MXS-4164)

  • The max_slave_replication_lag parameter could not be set to a non-zero value with Galera Monitor (galeramon). (MXS-4160)

  • 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)

  • When maxctrl call command is 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)

  • When maxctrl create monitor is executed, if some of the servers specified by the --servers option 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)

  • When maxctrl create listener is executed and ssl=true is specified, the ssl_ca_cert parameter is required, even though it should be optional. (MXS-4169)

  • When Xpand Monitor (xpandmon) is used, bootstrap nodes can't be defined using a hostname rather than an IP address. (MXS-4185)

    • 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)


In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 6.4.1 is provided for:

  • CentOS 7 (x86_64)

  • Debian 9 (x86_64, ARM64)

  • Debian 10 (x86_64, ARM64)

  • Debian 11 (x86_64, ARM64)

  • Red Hat Enterprise Linux 7 (x86_64)

  • Red Hat Enterprise Linux 8 (x86_64, ARM64)

  • Rocky Linux 8 (x86_64, ARM64)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)

  • Ubuntu 22.04 (x86_64, ARM64)