All pages
Powered by GitBook
1 of 1

Loading...

Release Notes for MariaDB Enterprise Server 10.3.22-6

This sixth release of 10.3 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.3.22-6 was released on 2020-03-02.

Fixed Security Vulnerabilities

CVE (with link)

* CVSS base score

Notable Changes

  • The systemd start and stop timeout for the MariaDB service is now set to 900 seconds (15 minutes). ()

  • For (Galera Library 25.3.29):

    • Setting 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 led to sub-optimal performance in high-bandwidth WAN clusters. The default value for has been changed to auto, which lets the kernel tune the TCP receive buffer. A new variable with a default value of auto

Issues Fixed

Can result in a hang or crash

  • During a server restart, recovery could encounter an out-of-memory condition. A restart was only possible after increasing . ()

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

  • On a rollback or during a background task to purge transaction history due to a SPATIAL INDEX, the server could hang. ()

Can result in unexpected behavior

  • Executing or on tables could lead to an unexpected SQL Error (1118): Row size too large, when (default). ()

  • Queries that use window functions and implicit grouping could return wrong results. ()

  • Queries which use DISTINCT COUNT(*) OVER() in the expression returned wrong results. ()

Related to installation or upgrade

  • Server could not be started when is set in a config file. (MENT-625)

Interface Changes

  • None

Platforms

In alignment with the , MariaDB Enterprise Server 10.3.22-6 is provided for:

  • Red Hat Enterprise Linux 8

  • Red Hat Enterprise Linux 7

  • Red Hat Enterprise Linux 6

  • CentOS 8

Some components of MariaDB Enterprise Server might not support all platforms. For additional information, see "".

Note

CentOS 6, Debian 8, and Red Hat Enterprise Linux 6 are no longer supported as per the . Older releases are available from the . Instructions for installation are included as a README file within the download.

was added to allow send buffer tuning.
Crashes could occur rarely when using ALTER TABLE ... IMPORT TABLESPACE (MDEV-21513)
  • Possible server crash if (default) is set and if the value for parameter pos in 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 is executed, and the replica reconnects using the GTID protocol. (MDEV-19376)

  • could encounter a deadlock if a backup is taken from a replica with slave-parallel-threads is set to a value greater than 0 (MDEV-21255)

  • could crash when used in combination with FLUSH TABLES``and``UNLOCK TABLES``(MENT-438)

  • The aria_pack utility crashed when running an offline datafile compression on a table. (MDEV-14183)

  • Dropping a partition with and SESSION caused the MariaDB Enterprise Cluster (Galera) node to hang. (MDEV-21189)

  • With active optimizer trace (optimizer_trace='enabled=on') server could crash or the data of the optimizer trace could become corrupted. (MENT-614)

  • 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.cnf was 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 BY with an expression containing a field of a view could return wrong results. (MDEV-20922)

  • Running the script mysql_tzinfo_to_sql for MariaDB Enterprise Cluster could result in inconsistent timezone information across different nodes. (MDEV-21209)

  • Using the option with would cause it to run out of memory. (MDEV-20679)

  • For MariaDB Enterprise Cluster (Galera Library 25.3.29):

    • 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 delays in messages relayed by the segment representative. The fix implements fair queuing of messages.

    • Due to a bug in quorum computation, two primary conflicting components were formed when the group merged and partitioned again while the new primary view was forming.

  • A range plan was not always used for multi-join queries. (MDEV-21383)

  • CentOS 7
  • CentOS 6

  • Ubuntu 18.04

  • Ubuntu 16.04

  • Debian 10

  • Debian 9

  • Debian 8

  • SUSE Linux Enterprise Server 15

  • SUSE Linux Enterprise Server 12

  • Microsoft Windows

  • 5.9

    MDEV-17571
    MDEV-19176
    MDEV-21509
    MDEV-21512
    MDEV-21429
    MDEV-21318
    MDEV-16579
    enterprise lifecycle
    MariaDB Corporation Engineering Policies
    MariaDB Engineering Policy
    MariaDB Downloads page
    cve.org
    CVE-2020-2574
    MariaDB Enterprise Cluster
    socket.recv_buf_size
    socket.recv_buf_size
    socket.recv_buf_size
    innodb_strict_mode=ON
    wsrep_OSU_method=RSU
    MariaDB Enterprise Server
    InnoDB
    innodb_buffer_pool_size
    TRUNCATE
    OPTIMIZE
    InnoDB
    lc_messages
    binlog_checksum=CRC32
    SHOW BINLOG EVENTS FROM pos
    RESET MASTER
    MariaDB Enterprise Backup
    MariaDB Enterprise Backup
    sql_log_bin=0
    --use-memory
    mariadb-backup

    This page is: Copyright © 2025 MariaDB. All rights reserved.