MySQL Lists are EOL. Please join:

List:General Discussion« Previous MessageNext Message »
From:Hery Ramilison Date:April 26 2019 5:08pm
Subject:MySQL Cluster 7.4.24 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
   - 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.4 makes significant advances in performance; operational
efficiency (such as enhanced reporting and faster restarts and upgrades)
and conflict detection and resolution for active-active replication
between MySQL Clusters.

MySQL Cluster 7.4.24 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.4.24 (5.6.44-ndb-7.4.24) (2019-04-26, 
General Availability)

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

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

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

    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.44 (see Changes in MySQL 5.6.44 (2019-04-25,
    General Availability)

Functionality Added or Changed

      * Building with CMake3 is now supported by the
        compile-cluster script included in the NDB source

Bugs Fixed

      * When a pushed join executing in the DBSPJ block had to
        store correlation IDs during query execution, memory for
        these was allocated for the lifetime of the entire query
        execution, even though these specific correlation IDs are
        required only when producing the most recent batch in the
        result set. Subsequent batches require additional
        correlation IDs to be stored and allocated; thus, if the
        query took sufficiently long to complete, this led to
        exhaustion of query memory (error 20008). Now in such
        cases, memory is allocated only for the lifetime of the
        current result batch, and is freed and made available for
        re-use following completion of the batch. (Bug #29336777)
        References: See also: Bug #26995027.

      * In some cases, one and sometimes more data nodes
        underwent an unplanned shutdown while running
        ndb_restore. This occurred most often, but was not always
        restircted to, when restoring to a cluster having a
        different number of data nodes from the cluster on which
        the original backup had been taken.
        The root cause of this issue was exhaustion of the pool
        of SafeCounter objects, used by the DBDICT kernel block
        as part of executing schema transactions, and taken from
        a per-block-instance pool shared with protocols used for
        NDB event setup and subscription processing. The
        concurrency of event setup and subscription processing is
        such that the SafeCounter pool can be exhausted; event
        and subscription processing can handle pool exhaustion,
        but schema transaction processing could not, which could
        result in the node shutdown experienced during
        This problem is solved by giving DBDICT schema
        transactions an isolated pool of reserved SafeCounters
        which cannot be exhausted by concurrent NDB event
        activity. (Bug #28595915)

      * ndb_restore did not restore autoincrement values
        correctly when one or more staging tables were in use. As
        part of this fix, we also in such cases block applying of
        the SYSTAB_0 backup log, whose content continued to be
        applied directly based on the table ID, which could
        ovewrite the autoincrement values stored in SYSTAB_0 for
        unrelated tables. (Bug #27917769, Bug #27831990)
        References: See also: Bug #27832033.

      * ndb_restore employed a mechanism for restoring
        autoincrement values which was not atomic, and thus could
        yield incorrect autoincrement values being restored when
        multiple instances of ndb_restore were used in parallel.
        (Bug #27832033)
        References: See also: Bug #27917769, Bug #27831990.

      * An NDB table having both a foreign key on another NDB
        table using ON DELETE CASCADE and one or more TEXT or
        BLOB columns leaked memory. (Bug #27484882)

      * When executing the redo log in debug mode it was possible
        for a data node to fail when deallocating a row. (Bug
        #93273, Bug #28955797)

On Behalf of Oracle/MySQL Release Engineering Team,
Hery Ramilison
MySQL Cluster 7.4.24 has been releasedHery Ramilison26 Apr