Release Notes for MariaDB Enterprise Server 10.4.12-6
This page is part of MariaDB's MariaDB Documentation.
The parent of this page is: Release Notes for MariaDB Enterprise Server 10.4
Topics on this page:
This sixth release of MariaDB Enterprise Server 10.4 is a maintenance release, including a variety of fixes.
MariaDB Enterprise Server 10.4.12-6 was released on 2020-03-02.
Fixed Security Vulnerabilities
CVE (with cve.mitre.org link)
CVSS base score
MariaDB ColumnStore 1.4.3 is included in this release. Specific details on this component may be found in the ColumnStore 1.4.3 release notes.
The systemd start and stop timeout for the MariaDB service is now set to 900 seconds (15 minutes). (MDEV-17571)
ENFORCEoption for parameter slave-run-triggers-for-rbr can now be used to assure that triggers defined on a table on the replica are executed for row based replication (RBR) when a trigger on a primary (master) exists for this table. The
LOGGINGoption already exists, but only allows to execute triggers on the replica for row based replication if no trigger exists for this table on the primary (master). (MENT-607)
On Windows: Removed a misleading
OS error 203logged by InnoDB in the error log when the datadir is defined as a network resource. (MDEV-21260)
For MariaDB Enterprise Cluster (Galera Library 26.4.4):
buf_was not effective because it was done after the socket was connected or accepted. The default value also caused TCP receive buffer auto-tuning to be disabled. This lead to sub-optimal performance in high bandwidth WAN clusters. The default value for socket.recv_ size buf_has been changed to size
auto, which lets the kernel tune the TCP receive buffer. A new variable
socket.send_buf_sizewith default value
autowas added to allow send buffer tuning.
Can result in crashes, hangs, stalls
During a server restart InnoDB recovery could encounter an out-of-memory condition. A restart was only possible after increasing innodb_
buffer_. (MDEV-19176) pool_ size
On a rollback of a large insert or update, or during a background task to purge transaction history after a large update or delete, the server could hang. (MDEV-21509)
On a rollback or during a background task to purge transaction history due to a
SPATIAL INDEX, the server could hang. (MDEV-21512)
Crashes could occur rarely when using
ALTER TABLE ... IMPORT TABLESPACE(MDEV-21513)
Possible server crash if binlog_
checksum=CRC32(default) is set and if the value for parameter
posin SHOW BINLOG EVENTS FROM pos does not point to the beginning of an event in the binary log. (MDEV-18046)
A replication primary (master) running in semi-sync mode could crash when RESET MASTER is executed and the replica reconnects using the GTID protocol. (MDEV-19376)
MariaDB Enterprise Backup could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads set to a value greater than
MariaDB Enterprise Backup could crash when used in combination with
aria_packutility crashed when running an offline datafile compress on a table. (MDEV-14183)
Dropping a partition with wsrep_
OSU_and SESSION sql_ method=RSU log_caused the MariaDB Enterprise Cluster (Galera) node to hang. (MDEV-21189) bin=0
Shutdown of a replica (slave) Server could hang when slave-parallel-threads is set to a value greater than
Using SET STATEMENT max_
statement_to set a timeout for the statement resulted in a crash. (MENT-634) time
Querying the wsrep_
onsystem status variable after enabling Galera Cluster Replication in MariaDB Enterprise Cluster for a running server could result in a crash. (MENT-633)
Can result in unexpected behavior
Executing TRUNCATE or OPTIMIZE on InnoDB tables could lead to an unexpected
SQL Error (1118): Row size too large, when innodb_
strict_(default). (MDEV-21429) mode=ON
Queries which use window functions and implicit grouping could return wrong results. (MDEV-21318)
Queries which use
DISTINCT COUNT(*) OVER()in the expression returned wrong results. (MDEV-16579)
Inefficient thread handling in the thread pool, impacting any application that uses the thread pool. (MDEV-21343)
The MariaDB Enterprise Server config file
mariadb-enterprise.cnfwas not registered as a config file in RPM packages. (MENT-591)
ALTER USER IF EXISTS generated a SQL syntax error. (MENT-643)
A query using
GROUP BYwith an expression containing a field of a view could return wrong results. (MDEV-20922)
Running the script
mysql_tzinfo_to_sqlfor MariaDB Enterprise Cluster could result in inconsistent timezone information across different nodes. (MDEV-21209)
Using the --use-memory option with mariabackup would cause it to run out of memory. (MDEV-20679)
A range plan was not always used for multi-join queries. (MDEV-21383)
An ALTER TABLE on an InnoDB table adding a new first column which is used to define system versioning period could lead to unexpected errors. This only happened when the transaction-based system version was used. (MDEV-18865, MDEV-18875)
For MariaDB Enterprise Cluster (Galera Library 26.4.4):
GCS delivered a JOIN message even if the node was in a DONOR state.
GCache could contain mixed histories from different clusters.
GComm socket timestamping/liveness checking produced false positives during replication of large transactions, which caused excessive amounts of broken connections.
Large transactions were able to monopolize bandwidth when segmentation was configured, causing delayed in messages relayed by segment representative. The fix implements fair queuing of messages.
Due to a bug in quorum computation, two primary conflicting primary components were formed when the group merged and partitioned again while the new primary view was forming.
Related to installation or upgrade
Server could not be started when lc_
messagesis set in a config file. (MENT-625)
schema_system variable default value changed from max_ cond_ classes
In alignment to the enterprise lifecycle, MariaDB Enterprise Server 10.4.12-6 is provided for:
Red Hat Enterprise Linux 8
Red Hat Enterprise Linux 7
Red Hat Enterprise Linux 6
SUSE Linux Enterprise Server 15
SUSE Linux Enterprise Server 12
Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "MariaDB Corporation Engineering Policies".
CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the MariaDB Engineering Policy. Older releases are available from the MariaDB Downloads page. Instructions for installation are included as a
README file within the download.