MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.4.29 has been released
Posted by: Surabhi Bhat
Date: July 14, 2020 02:18AM

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

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.29 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.29 (5.6.49-ndb-7.4.29) (2020-07-14, General Availability)

   MySQL NDB Cluster 7.4.29 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.49
   (see Changes in MySQL 5.6.49 (2020-07-13, General Availability)
   ( )).

Bugs Fixed

     * During a node restart, the SUMA block of the node that is
       starting must get a copy of the subscriptions (events with
       subscribers) and subscribers (NdbEventOperation instances which
       are executing) from a node already running. Before the copy is
       complete, nodes which are still starting ignore any user-level
       SUB_START or SUB_STOP requests; after the copy is done, they can
       participate in such requests. While the copy operation is in
       progress, user-level SUB_START and SUB_STOP requests are blocked
       using a DICT lock.  An issue was found whereby a starting node
       could participate in SUB_START and SUB_STOP requests after the
       lock was requested, but before it is granted, which resulted in
       unsuccessful SUB_START and SUB_STOP requests.  This fix ensures
       that the nodes cannot participate in these requests until after
       the DICT lock has actually been granted. (Bug #31302657)

     * An excessive number of entries were written to the backup
       log when performing an online backup, using ndbmtd on the data
       nodes. This happened because row changes occurring to fragments
       managed by LDM instance 1 were always recorded in the log, even
       when they were for primary fragments other than primary
       fragments. This wasted resources when restoring from the backup,
       and could cause other problems when doing so, such as when using
       staging tables for schema transforms while executing ndb_restore.
       (Bug #31034270)

     * The Dojo toolkit included with NDB Cluster and used by
       the Auto-Installer was upgraded to version 1.15.3. (Bug

     * A packed version 1 configuration file returned by
       ndb_mgmd could contain duplicate entries following an upgrade to
       NDB 8.0, which made the file incompatible with clients using
       version 1. This occurs due to the fact that the code for handling
       backwards compatibility assumed that the entries in each section
       were already sorted when merging it with the default section. To
       fix this, we now make sure that this sort is performed prior to
       merging.  (Bug #31020183)

     * When executing any of the SHUTDOWN, ALL STOP, or ALL
       RESTART management commands, it is possible for different nodes
       to attempt to stop on different global checkpoint index (CGI)
       boundaries. If they succeed in doing so, then a subsequent system
       restart is slower than normal because any nodes having an earlier
       stop GCI must undergo takeover as part of the process. When nodes
       failing on the first GCI boundary cause surviving nodes to be
       nonviable, surviving nodes suffer an arbitration failure; this
       has the positive effect of causing such nodes to halt at the
       correct GCI, but can give rise to spurious errors or similar.  To
       avoid such issues, extra synchronization is now performed during
       a planned shutdown to reduce the likelihood that different data
       nodes attempt to shut down at different GCIs as well as the use
       of unnecessary node takeovers during system restarts. (Bug

On Behalf of MySQL Release Engineering Team,
Surabhi Bhat

Options: ReplyQuote

Written By
MySQL Cluster 7.4.29 has been released
July 14, 2020 02:18AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.