MySQL Lists are EOL. Please join:

List:Announcements« Previous MessageNext Message »
From:Piotr Obrzut Date:October 23 2018 7:03pm
Subject:MySQL Cluster 7.3.23 has been released
View as plain text  
Dear MySQL Users,

MySQL Cluster is the distributed, shared-nothing variant of MySQL.
This storage engine provides:

   - In-Memory storage - Real-time performance (with optional
     checkpointing to disk)
   - Transparent Auto-Sharding - Read & write scalability
   - Active-Active/Multi-Master geographic replication
   - 99.999% High Availability with no single point of failure
     and on-line maintenance
   - NoSQL and SQL APIs (including C++, Java, http, Memcached
     and JavaScript/Node.js)

MySQL Cluster 7.3.23, has been released and can be downloaded from

where you will also find Quick Start guides to help you get your
first MySQL Cluster database up and running.

The release notes are available from

MySQL Cluster enables users to meet the database challenges of next
generation web, cloud, and communications services with uncompromising
scalability, uptime and agility.

More details can be found at

Enjoy !

Changes in MySQL NDB Cluster 7.3.23 (5.6.42-ndb-7.3.23) (Not yet
released, General Availability)

    MySQL NDB Cluster 7.3.23 is a new release of NDB Cluster,
    based on MySQL Server 5.6 and including features from version
    7.3 of the NDB storage engine, as well as fixing a number of
    recently discovered bugs in previous NDB Cluster releases.

    Obtaining MySQL NDB Cluster 7.3.  MySQL NDB Cluster 7.3
    source code and binaries can be obtained from

    For an overview of changes made in MySQL NDB Cluster 7.3, see
    What is New in NDB Cluster 7.3

    This release also incorporates all bug fixes and changes made
    in previous NDB Cluster releases, as well as all bug fixes
    and feature changes which were added in mainline MySQL 5.6
    through MySQL 5.6.42 (see Changes in MySQL 5.6.42 (Not yet
    released, General Availability)

Bugs Fixed

      * Having a large number of deferred triggers could
        sometimes lead to job buffer exhaustion. This could
        due to the fact that a single trigger can execute
        operations---for example, a foreign key parent
        may perform operations on multiple matching child
        rows---and that a row operation on a base table can
        execute multiple triggers. In such cases, row
        are executed in batches. When execution of many
        was deferred---meaning that all deferred triggers
        executed at pre-commit---the resulting concurrent
        execution of a great many trigger operations could
        the data node job buffer or send buffer to be
        leading to failure of the node.
        This issue is fixed by limiting the number of
        trigger operations as well as the number of trigger
        requests outstanding per transaction.
        For immediate triggers, limiting of concurrent
        operations may increase the number of triggers
waiting to
        be executed, exhausting the trigger record pool and
        resulting in the error Too many concurrently fired
        triggers (increase MaxNoOfFiredTriggers. This can be
        avoided by increasing MaxNoOfFiredTriggers, reducing
        user transaction batch size, or both. (Bug
        References: See also: Bug #18229003, Bug #27310330.

On Behalf of Oracle/MySQL Release Engineering Team
Piotr Obrzut

MySQL Cluster 7.3.23 has been releasedPiotr Obrzut23 Oct