Release Notes for MariaDB Enterprise Server 10.6.5-2
This page is part of MariaDB's Documentation.
The parent of this page is: Release Notes for MariaDB Enterprise Server 10.6
Topics on this page:
Overview
MariaDB Enterprise Server 10.6.5-2 is a maintenance release of MariaDB Enterprise Server 10.6. This release includes a variety of fixes.
MariaDB Enterprise Server 10.6.5-2 was released on 2021-12-13.
Fixed Security Vulnerabilities
CVE (with cve.org link) | CVSS base score |
7.5 | |
7.5 | |
6.5 | |
5.5 |
Notable Changes
Galera updated to 26.4.10.
Debian 11 support added.
Enterprise Spider no longer enables pushdown of UDFs and Stored Functions to the Data Node by default: (MDEV-26545)
The default value of
spider_use_pushdown_udf
has changed from-1
to0
In previous releases, Enterprise Spider pushed UDFs and Stored Functions down to the Data Node by default, which could cause query results to be inconsistent.
Starting with this release, all UDFs and stored functions are evaluated on the Spider Node by default. If desired, pushdown of UDFs and Stored Functions can be explicitly enabled by setting
spider_use_pushdown_udf=1
. Testing is recommended to confirm that query results are consistent.
Performance Schema tables provide descriptions of each column in the
COMMENT
column option. (MDEV-25325)In the Spider ODBC Topology, Enterprise Spider automatically sets the appropriate transaction isolation level for the ODBC data source. (MENT-1328)
The InnoDB Force Recovery procedure has changed to differentiate between rollback of DDL and DML operations. The changes are: (MDEV-25683)
The behavior of
innodb_force_recovery
is no longer identical wheninnodb_force_recovery=3
andinnodb_force_recovery=4
When
innodb_force_recovery=3
is set, InnoDB skips rollback of DML operations, but DDL operations will still be rolled back using the DDL log.When
innodb_force_recovery=4
is set, InnoDB skips rollback of both DML and DDL operations. This behavior is equivalent to settinginnodb_force_recovery=3
in versions earlier than MariaDB Enterprise Server 10.6.5.
Issues Fixed
Can result in data loss
InnoDB tables with
ROW_FORMAT=COMPRESSED
could be corrupted. (MENT-1367)
Can result in a hang or crash
MariaDB Enterprise Cluster, powered by Galera, can crash on
INSERT
if the table does not have a primary key and if the data for a field exceeds 4096 bytes. (MDEV-24978)When an InnoDB tablespace (
.ibd
) file is imported usingALTER TABLE .. IMPORT TABLESPACE
without a corresponding.cfg
file, InnoDB causes a server crash. (MDEV-26131, MDEV-20931)When
OPTIMIZE TABLE
(ormariadb-check -o
) is executed against an InnoDB table with aFULLTEXT
index, InnoDB can cause a server crash. (MDEV-25702, MENT-1198)Resolving aggregate functions that are used in a view can cause in a crash. (MDEV-24454)
Executing
CREATE OR REPLACE TABLE AS SELECT
underLOCK TABLE
can cause in a crash. (MDEV-23391)If two InnoDB tables have a foreign key and an operation cascades from the parent table to the child table, an index on a virtual generated column in the child table can become corrupt. (MDEV-26866)
MariaDB Enterprise Cluster, powered by Galera, crashes with errors like:
[ERROR] WSREP: Trx 236236 tries to abort slave trx 236238
(MDEV-25835)Server crashes when a table uses a sequence as a column default (DEFAULT NEXT_
VALUE(my_ ) and the table is used concurrently by both a prepared statement and a normal statement. (MDEV-22785)seq) InnoDB causes server crash when a table is converted from
utf8mb3
toutf8mb4
(MDEV-25951)When enabling MariaDB Enterprise Audit, server crash can occur. (MENT-1307)
MariaDB Enterprise Audit occasionally hangs when rotating logs. (MENT-1339)
On 64-bit Microsoft Windows when MyISAM accesses key buffer and key_
buffer_ is greater than 4 GB, the server crashes. (MDEV-26533)size Using
SET GLOBAL innodb_purge_threads
to increaseinnodb_purge_threads
, may cause a hang. (MENT-1331)Enterprise Spider causes server crash when an
ALTER TABLE
operation requires access to a Data Node. (MDEV-26539)InnoDB persistent statistics causes server to hang. (MDEV-15020)
On an InnoDB table, when a DDL statement rebuilds the parent table in a foreign key relationship, a concurrent
INSERT
into the child table sometimes causes a crash. (MDEV-26554)On an InnoDB table, when the server crashes or is killed while a
DROP TABLE
or table-rebuildingALTER TABLE
operation is being executed, InnoDB causes a server crash during crash recovery, which occurs after the server has restarted. (MENT-1368)InnoDB sometimes causes server crash during
ALTER TABLE .. IMPORT TABLESPACE
when the imported tablespace contains columns that have been instantly reordered or dropped. The MariaDB error log contains the following error message: (MDEV-18543)Schema mismatch (Index field name newcol doesn't match tablespace metadata field name name for field position...
MariaDB Enterprise Cluster causes server crash when
wsrep_on=OFF
is set and transactions are in progress. (MENT-1236)
Can result in unexpected behavior
skip_networking
does not prevent replication. (MDEV-24969)MariaDB Enterprise Cluster joiner node incorrectly uses
localhost
for TLS certificate verification and fails to join cluster whenwsrep_sst_method=mariabackup
andencrypt=3
are configured. (MDEV-26360)mariadb --binary-mode
is not able to replay somemysqlbinlog
outputs if\\0
is in the data. (MDEV-25444)Memory leak with row-based replication can lead to high memory usage on replica servers. (MDEV-26712)
SHOW CREATE VIEW
andmariadb-dump
generate invalid SQL for some complex views. (MDEV-26299)When statement-based or mixed replication is used and a DML statement encounters an error in a transaction that creates or drops a temporary table, non-committed writes to transactional tables can be incorrectly replicated to replica servers. (MDEV-26833)
MariaDB Enterprise Cluster joiner node fails to join cluster when
wsrep_sst_method=mariabackup
and Backward Compatible SST TLS Mode is configured. (MDEV-26211)Spider does not work correctly for UDF and stored functions if used in a query's
WHERE
conditions. (MDEV-26545)If an
INVISIBLE
column has a computed default value, anINSERT
statement that doesn't specify a value for the column causes the default value to be ignored. (MDEV-25891)Password validation plugins (including
simple_password_check
) cause a user's existing password hash to be removed from the server's in-memory privilege cache when the user tries to change their password to an invalid password. (MDEV-26650)With MariaDB Enterprise Cluster, a
TRUNCATE
on a table with a Foreign Key Constraint is not replicated to other nodes. (MDEV-26053)InnoDB's adaptive purging can decrease throughput by starving user threads after
dict_sys.mutex
removal. (MDEV-26356)CONNECTION_ID
column isNULL
ininformation_schema.THREAD_POOL_QUEUES
(MDEV-26440)The server in some cases shows decreasing performance with notes
InnoDB: Cannot close file...
in the error log. This issue occurs only whenopen-files-limit
is reached and alog-checkpoint
is triggered. (MDEV-25215)XA PREPARE
sometimes leads to lock wait timeouts on replica servers. (MDEV-26682)Replica server does not invalidate query cache after replicating table updates. (MENT-1360)
MariaDB Enterprise Cluster, powered by Galera, shows inconsistent values for
wsrep_apply_window
andwsrep_commit_window
when comparingperformance_schema.galera_group_members
andinformation_schema.GLOBAL_STATUS
(MENT-1333)MariaDB Enterprise Cluster incorrectly streams XA transactions when
wsrep_trx_fragment_unit=statements
is set, which causes errors when the fragment is applied. (MENT-1344)With MariaDB Enterprise Cluster, a replica server replicating from a MariaDB Enterprise Cluster node incorrectly uses the primary server's
server_id
andwsrep_gtid_domain_id
values to generate GTIDs for local transactions. (MDEV-26250)MariaDB Enterprise Backup does not write the current GTID to
xtrabackup_binlog_info
when a MariaDB Enterprise Cluster node is backed up andwsrep_gtid_mode=ON
is set. (MDEV-26237)When a new MariaDB Enterprise Cluster node is bootstrapped with
wsrep_gtid_mode=ON
set, the node's configuredserver_id
andwsrep_gtid_domain_id
values are overridden by the values present in the node's binary logs. (MDEV-26223)With MariaDB Enterprise Cluster, changes to
wsrep_gtid_domain_id
inmy.cnf
are ignored on node restart. (MDEV-25115)
Related to install and upgrade
On CentOS 7,
auth_pam_tool
has incorrect permissions. (MDEV-26380)Running
mariadb-upgrade
with no'root'@'localhost'
user may fail with the messageThe user specified as a definer ('root'@'localhost') does not exist FATAL ERROR: Upgrade failed
. (MDEV-26925)
Changes in Storage Engines
This release originally incorporated MariaDB ColumnStore storage engine version 6.2.2.
This release now incorporates MariaDB ColumnStore storage engine version 6.2.3.
Platforms
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.6.5-2 is provided for:
CentOS 7 (x86_
64) Debian 9 (x86_
64, ARM64) Debian 10 (x86_
64, ARM64) Debian 11 (x86_
64, ARM64) Microsoft Windows (x86_
64) Red Hat Enterprise Linux 7 (x86_
64) Red Hat Enterprise Linux 8 (x86_
64, ARM64) SUSE Linux Enterprise Server 12 (x86_
64) SUSE Linux Enterprise Server 15 (x86_
64, ARM64) Ubuntu 18.04 (x86_
64, ARM64) Ubuntu 20.04 (x86_
64, ARM64)
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
Installation Instructions
Enterprise Cluster Topology with MariaDB Enterprise Server 10.6
Primary/Replica Topology with MariaDB Enterprise Server 10.6
HTAP Topology with MariaDB Enterprise Server 10.6 and MariaDB Enterprise ColumnStore 6
Single-Node Enterprise ColumnStore 6 with MariaDB Enterprise Server 10.6 and Object Storage
Single-Node Enterprise ColumnStore 6 with MariaDB Enterprise Server 10.6
Enterprise Spider Sharded Topology with MariaDB Enterprise Server 10.6
Enterprise Spider Federated Topology with MariaDB Enterprise Server 10.6