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.

Notable Changes

  • Improvements to the MaxGUI query editor visualization feature. (MXS-4059)

  • When using maxctrl show sessions or maxctrl list sessions the remote client's port number is now displayed in addition to the remote client's IP address. (MXS-4084)

Issues Fixed

Can result in a hang or crash

Can result in unexpected behavior

  • When Schema Router (schemarouter) is used, the sys schema is not automatically ignored for duplicate checks. (MXS-4110)

  • With the MaxScale REST API, the /user/inet endpoint fails schema validation when used with the newest schema for the JSON API specification. (MXS-4109)

  • Executing the SHOW SLAVE STATUS statement via the MaxScale Binlog router (binlogrouter) does not show SSL information. (MXS-4096)

  • Duplicate table errors for tables where the table names are in different cases, for example table.t1 and table.T1 (MXS-4092)

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

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

  • When multiple servers are selected as Master with Read Connection Router (readconnroute), the rank parameter is ignored for all servers except the last one. (MXS-4132)

  • When a service uses the targets parameter to route queries to a second service, the second service is not shown as a target in the output of maxctrl list services. (MXS-4127)

  • When the Read/Write Split router (readwritesplit) is configured with use_sql_variables_in=master, the query is routed normally but the following error is logged: (MXS-4111)

    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`.
  • Avro router (avrorouter) with CDC to Kafka can fail for some tables. (MXS-4095)

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


In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 6.3.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)

  • SUSE Linux Enterprise Server 15 (x86_64, ARM64)

  • Ubuntu 18.04 (x86_64, ARM64)

  • Ubuntu 20.04 (x86_64, ARM64)