MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.4.25 has been released
Posted by: Jocelyn Ramilison
Date: July 23, 2019 01:56AM

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.25 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.25 (5.6.45-ndb-7.4.25) (2019-07-23,
General Availability)

   MySQL NDB Cluster 7.4.25 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.45 (see Changes in MySQL 5.6.45 (2019-07-22,
   General Availability)

Bugs Fixed

     * The requestInfo fields for the long and short forms of
       the LQHKEYREQ signal had diffferent definitions; bits
       used for the key length in the short version were reused
       for flags in the long version, since the key length is
       implicit in the section length of the long version of the
       dignal but it was possible for long LQHKEYREQ signals to
       contain a keylength in these same bits, which could be
       misinterpreted by the receiving local query handler,
       potentially leading to errors. Checks have now been
       implemented to make sure that this no longer happens.
       (Bug #29820838)

     * When restoring TINYBLOB columns, ndb_restore now treats
       them as having the BINARY character set. (Bug #29486538)

     * Restoration of epochs by ndb_restore failed due to
       temporary redo errors. Now ndb_restore retries epoch
       updates when such errors occur. (Bug #29466089)

     * ndb_restore --restore-epoch incorrectly reported the stop
       GCP as 1 less than the actual position. (Bug #29343655)

     * Added support which was missing in ndb_restore for
       conversions between the following sets of types:

          + BLOB and BINARY or VARBINARY columns

          + TEXT and BLOB columns

          + BLOB columns with unequal lengths

          + BINARY and VARBINARY columns with unequal lengths
       (Bug #28074988)

     * Restore points in backups created with the SNAPSHOTSTART
       option (see Using The NDB Cluster Management Client to
       Create a Backup
       were not always consistent with epoch boundaries.
       (Bug #27566346) References: See also: Bug #27497461.

On Behalf of Oracle/MySQL Release Engineering Team,
Hery Ramilison

Options: ReplyQuote

Written By
MySQL Cluster 7.4.25 has been released
July 23, 2019 01:56AM

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.