Release Notes for MariaDB MaxScale 22.08.5
This page is part of MariaDB's Documentation.
The parent of this page is: Release Notes for MariaDB MaxScale 22.08
Topics on this page:
Overview
MariaDB MaxScale is an advanced database proxy and query router. MaxScale is a component of MariaDB database products.
MariaDB MaxScale 22.08.5 was released on 2023-03-28. This release is of General Availability (GA) maturity.
This document describes the changes in MaxScale 22.08.5
when compared to MaxScale 22.08.4
.
Issues Fixed
Can result in a hang or crash
When the internal query parser throws an exception, the Binlog Router (
binlogrouter
) does not catch it. (MXS-4510)In previous releases, this could occur when a
SET
statement is used to modifygtid_slave_pos
and the file where the GTID is stored is unavailable.Starting with this release, Binlog Router (
binlogrouter
) catches exceptions from the internal parser.
If a MaxScale listener receives an invalid packet, MaxScale can hang. (MXS-4488)
MaxScale crashes when trying to create a table named
DUAL
. (MXS-4481)
Can result in unexpected behavior
When a binary log event is larger than
INT_MAX
(2,147,483,647) bytes, Binlog Router (binlogrouter
) causes an integer overflow when it calculates the event length, which can lead to excessive memory allocation and errors. (MXS-4557)Starting with this release, Binlog Router (
binlogrouter
) can properly handle binary log events larger thanINT_MAX
(2,147,483,647) bytes.
When the
authenticator_options='lower_case_table_names=1'
is set, database names are not checked in a case insensitive manner. (MXS-4556)When a server is down, MaxScale does not know the server's MariaDB Server version, and MaxScale can make incorrect assumptions about the server version that can negatively impact how it classifies and routes queries. (MXS-4524)
In previous releases, MaxScale's incorrect assumptions about the server version can cause the internal query classifier to incorrectly classify sequence operations as read queries.
Starting with this release, when MaxScale does not know a server's version, the server is ignored when calculating the minimum and maximum server versions to prevent the query classifier from using the wrong version number.
When
writeq_high_water
is non-zero, a session can end up in an inconsistent state when the session is closed while network traffic throttling is in effect. (MXS-4515)The
skip_name_resolve
parameter is not dynamic. (MXS-4514)Starting with this release, the
skip_name_resolve
parameter is configurable at runtime (dynamic).
When the
masking
filter is used and the masking rules use host wildcards in theapplies_to
orexempted
attributes, user hosts are not interpreted properly, which can cause users to incorrectly receive unmasked results. (MXS-4504)When Binlog Filter is used to exclude events, replication can fail with an error. (MXS-4494)
In previous releases, the following errors could occur:
[ERROR] Unexpected break of being relay-logged GTID 0-3000-11 event group by the current GTID event 0-3000-12 [ERROR] Slave I/O: Relay log write failure: could not queue event from master, Internal MariaDB error code: 1595
Starting with this release, when statement-based replication is used and a query event is excluded, the query string in the event is replaced with an SQL comment. This causes the query event to do nothing and prevents the event from modifying the contents of the database. The GTID position of the database being replicated will still advance, which means that servers that replicate from it continue to function correctly.
MaxScale uses the default collation for the character set instead of the collation defined for the server. (MXS-4489)
For parameters that accept regular expressions (regex), the empty string (
""
) and an empty pattern ("//"
) are not handled the same. (MXS-4547)In previous releases, an empty pattern (
"//"
) is not handled as empty, but the empty string (""
) is.Starting with this release, both the empty string (
""
) and an empty pattern ("//"
) are handled as empty.
When a transaction fails checksum verification and
transaction_replay_retry_on_mismatch
is enabled,readwritesplit
can try to replay the failed transaction in an infinite loop. (MXS-4540)When configuration synchronization is enabled with the
config_sync_cluster
parameter, themaxscale_config
table is created in themysql
database. (MXS-4499)In previous releases, creating the
maxscale_config
table in themysql
database could cause some limitations, such as the inability to create triggers on the table.Starting with this release, the
config_sync_db
parameter can be used to configure the database used to create themaxscale_config
table. For backward compatibility, the default value ismysql
.
QLA filter does not properly log
USE
statements. (MXS-4410)When using MaxGUI, the Connections graph jumps from zero to the current value when the graph is refreshed. (MXS-4513)
When MaxScale requests the capabilities from a filter, the static capabilities are returned instead of the dynamic capabilities. (MXS-4555)
In previous releases, for all filters except
nullfilter
, the static capabilities are identical to the dynamic capabilities. Therefore, the impact of this issue are minimal.Starting with this release, all filters return dynamic capabilities.
When
connection_keepalive=0s
is set for areadconnroute
service, prepared statements are not tracked properly, which causes inaccurate warnings to be raised. (MXS-4552)In previous releases, the following warning could be incorrectly raised:
Unknown prepared statement handler (HANDLER_ID) given to MaxScale for COMMAND by 'USER'@'HOST'
Starting with this release, the prepared statements are tracked properly, so the warnings are not raised.
Interface Changes
config_sync_db
added to maxscale.maxscale
Platforms
In alignment to the MariaDB Corporation Engineering Policy, MariaDB MaxScale 22.08.5 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) Red Hat Enterprise Linux 9 (x86_
64, ARM64) Rocky Linux 8 (x86_
64, ARM64) Rocky Linux 9 (x86_
64, ARM64) SUSE Linux Enterprise Server 15 (x86_
64, ARM64) Ubuntu 18.04 (x86_
64, ARM64) Ubuntu 20.04 (x86_
64, ARM64) Ubuntu 22.04 (x86_
64, ARM64)