Release Notes for MariaDB MaxScale 6.4.0

When Binlog Router (binlogrouter) is used, a race condition can cause MaxScale to crash. (MXS-4138)

If the MaxScale node is disconnected from the Redis server when the Cache Filter (cache) is used, established connections can hang after executing a query that requires MaxScale to access the cache. (MXS-4105)

When the connection_keepalive parameter is 0, a memory leak can cause MaxScale to crash. (MXS-4100)

When Schema Router (schemarouter) is used and duplicate table checks are not disabled with the ignore_tables_regex parameter, the cost of performing the duplicate table check grows very quickly as the number of tables increases. (MXS-4151)

When Schema Router (schemarouter) is used, the cost of routing queries grows very quickly as the number of tables increases. (MXS-4152)

When the connection_keepalive parameter is non-zero, MaxScale sends pings to servers even if the client is idle. (MXS-4139)

• Starting with this release, when the connection_keepalive parameter is non-zero, MaxScale will only send pings to servers if the client has been idle for less than the connection_keepalive value.

When MariaDB Monitor (mariadbmon) performs failover, MaxScale writes a CHANGE MASTER TO statementCHANGE MASTER TO statement containing the replication user's user name and password in plain text to the MaxScale Log. (MXS-4115)

• Starting with this release, the user name and password are masked in the statement written to the MaxScale Log.

When Named Server Filter (namedserverfilter) is used, the targetXY parameter can route to servers, but not to services. (MXS-4113)

• Starting with this release, the targetXY parameter can route to servers and services.

When the MaxScale package is installed, the /etc/maxscale.cnf.d/ directory is not automatically created. (MXS-4134)