Release Notes for MariaDB MaxScale 6.4.1

When the Read/Write Split Router (readwritesplit) is used, MaxScale can hang when modifying sequence numbers in TCP packets. (MXS-4172)

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)

• In earlier releases, when the max_slave_replication_lag parameter 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.
  

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)