MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.5.22 has been released
Posted by: Rafal Molenda
Date: April 21, 2021 01:40PM

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 and http)

MySQL Cluster 7.5.22 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.5.22 (5.7.34-ndb-7.5.22) (2021-04-21, General Availability)

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

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

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

   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.7
   through MySQL 5.7.33 (see Changes in MySQL 5.7.33
   (2021-01-18, General Availability)

Bugs Fixed

     * Running out of disk space while performing an NDB backup
       could lead to an unplanned shutdown of the cluster. (Bug

     * The default number of partitions per node (shown in
       ndb_desc output as PartitionCount) is calculated using
       the lowest number of LDM threads employed by any single
       live node, and was done only once, even after data nodes
       left or joined the cluster, possibly with a new
       configuration changing the LDM thread count and thus the
       default partition count. Now in such cases, we make sure
       the default number of partitions per node is recalculated
       whenever data nodes join or leave the cluster. (Bug

Options: ReplyQuote

Written By
MySQL Cluster 7.5.22 has been released
April 21, 2021 01:40PM

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.