Release Notes for MariaDB MaxScale 6.3.1
MariaDB MaxScale is an advanced database proxy, firewall, and query router.
MariaDB MaxScale 6.3.1 was released on 2022-05-16. This release is of General Availability (GA) maturity.
Can Result in a Hang or Crash
alert : MaxScale 6.3.0 received fatal signal 11. alert : Statement currently being classified: none/unknown
Using a mix of MariaDB 10.2.7 and MariaDB 10.6 back-ends can cause MaxScale to crash. (MXS-4101)
Can Result in Unexpected Behavior
In earlier releases, this could impact query routing in some configurations. For example, let's say that two servers are selected as
Master: the first has
rank=primary, and the second has
router_options=masteris set, Read Connection Router (
readconnroute) chooses the second server, because the rank of the first server is ignored.
error : (1) [readwritesplit] (RW-Split-Router); Can't route COM_QUERY 'SELECT CASE data WHEN 'hello' THEN @var:=2 ELSE @var:=1 END'. SELECT with session data modification is not supported with `use_sql_variables_in=all`.
Starting with this release, Schema Router (
schemarouter) will automatically ignore the
sysschema for duplicate checks.
With the MaxScale REST API, the
/user/inetendpoint fails schema validation when used with the newest schema for the JSON API specification. (MXS-4109)
Duplicate table errors for tables where the table names are in different cases, for example
Starting with this release, Schema router (schemarouter) compares table and database names case-sensitively. This means that the tables test.t1 and test.T1 are seen as different tables.
Prior to this release, Schema router (schemarouter) compares table and database names case-insensitively. This can cause duplicate tables to be found if the server supports case-sensitive table names.
MaxScale deployments using Redis and the Spyder IDE tool fail with the error
(OperationalError: (2013, 'Lost connection to MySQL server during query'))(MXS-4091)
In MaxGUI, the parameter's tooltip shows unnecessary attributes. (MXS-4088)
The MaxScale REST API is inaccessible after deleting the last REST API user. (MXS-4086)
Starting with this release, it is no longer possible to delete all the REST API users. There will always be one user, "the last user", remaining.
Prior to this release, it is possible to delete every user of the REST API which would leave the REST API inaccessible.
In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 6.3.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_
SUSE Linux Enterprise Server 15 (x86_
Ubuntu 18.04 (x86_
Ubuntu 20.04 (x86_