Release Notes for MariaDB MaxScale 2.5.10

Issues Fixed

• COM_FIELD_LIST classified as a write. (MXS-3450)

• MaxScale sets MASTER_GTID_WAIT timeout to zero when causal_reads_timeout is less than 1 second. (MXS-3449)

• Logs are written while maxlog is disabled. (MXS-3448)

• SET DEFAULT ROLE is not classified as a write. (MXS-3445)

• Packets are sent out of order. This may result in a client-side "Packet received out-of-order. Expected 1; got 3." error. (MXS-3436)

• Monitor does not set session auto-commit when it has connected to a server first. (MXS-3433)

• Regression in Galera Monitor. This may result in an error "The 'INFORMATION_SCHEMA.SESSION_STATUS' feature is disabled; see the documentation for 'show_compatibility_56'" (MXS-3427)

Platforms

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

• CentOS 7

• Debian 9

• Debian 10

• Red Hat Enterprise Linux 7

• Red Hat Enterprise Linux 8

• SUSE Linux Enterprise Server 12

• SUSE Linux Enterprise Server 15

• Ubuntu 18.04

• Ubuntu 20.04

Installation

• Deploy Xpand Topology with MariaDB MaxScale 2.5

• Deploy Enterprise Cluster Topology with MariaDB MaxScale 2.5Deploy Enterprise Cluster Topology with MariaDB MaxScale 2.5

• Deploy Primary/Replica Topology with MariaDB MaxScale 2.5Deploy Primary/Replica Topology with MariaDB MaxScale 2.5

• Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 2.5Deploy ColumnStore Object Storage Topology with MariaDB MaxScale 2.5

• Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 2.5Deploy ColumnStore Shared Local Storage Topology with MariaDB MaxScale 2.5

Upgrades

• Upgrade to MariaDB MaxScale 2.5