Release Notes for MariaDB Enterprise Server 10.2.27-3

This third release of MariaDB Enterprise Server 10.2 is a maintenance release, including a variety of fixes.

MariaDB Enterprise Server 10.2.27-3 was released on 2019-09-30.

Issues Fixed

Can result in data loss

• Due to a race condition in InnoDB, an exclusive lock to an inserted record could be wrongly granted to multiple transactions when the transaction commits. This could lead to a server crash or data loss. ()

• INSERT...ON DUPLICATE KEY UPDATE, when there is more than one key, could result in inconsistent data between Primary and replica for replication mode and . This has been fixed for MIXED, but cannot be controlled by the replication for STATEMENT based replication.

• Inconsistent replicas need to be set up again from the Primary. ()

Can result in a hang or crash

• Replication could hang for transactions as has its own concurrency control . ()

Can result in unexpected behavior

• After setting it is possible to drop indexes from referenced (parent) tables, which could cause to behave as if table doesn't exist in engine ()

• Corner case where could fail because encrypted data files could not be copied if created shortly before the backup was started. ()

• could fail in the prepare face if the redo log is bigger than 512GB. ()

Related to performance

• Optimized scanning of the undo log versions while scanning the secondary index versions. ()

Interface Changes

• None.

Platforms

In alignment with the , MariaDB Enterprise Server 10.2.27-3 is provided for:

• CentOS 8

• CentOS 7

• CentOS 6

• Debian 10

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.

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