MySQL Cluster 7.2.32 has been released

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

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

http://www.mysql.com/downloads/cluster/

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

http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html

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

http://www.mysql.com/products/cluster/

Enjoy !

Changes in MySQL NDB Cluster 7.2.32 (5.5.59-ndb-7.2.32) (2018-01-17, 
General Availability)

    MySQL NDB Cluster 7.2.32 is a new release of NDB Cluster,
    incorporating new features in the NDB storage engine, and fixing
    recently discovered bugs in previous MySQL NDB Cluster 7.2
    development releases.

    Obtaining MySQL NDB Cluster 7.2.  MySQL NDB Cluster 7.2 source code
    and binaries can be obtained from
http://dev.mysql.com/downloads/cluster/ 
<http://dev.mysql.com/downloads/cluster/>.

    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.5 through MySQL 5.5.59
    (see Changes in MySQL 5.5.59 (Not yet released, General availability)
    (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-59.html)).

    Bugs Fixed

      * NDB Replication: On an SQL node not being used for a
        replication channel with sql_log_bin=0 it was possible after
        creating and populating an NDB table for a table map event to be
        written to the binary log for the created table with no
        corresponding row events. This led to problems when this log was
        later used by a slave cluster replicating from the mysqld where
        this table was created.  Fixed this by adding support for
        maintaining a cumulative any_value bitmap for global checkpoint
        event operations that represents bits set consistently for all
        rows of a specific table in a given epoch, and by adding a check
        to determine whether all operations (rows) for a specific table
        are all marked as NOLOGGING, to prevent the addition of this
        table to the Table_map held by the binlog injector.  As part of
        this fix, the NDB API adds a new getNextEventOpInEpoch3() method
        which provides information about any AnyValue received by making
        it possible to retrieve the cumulative any_value bitmap.  (Bug
        #26333981)

      * The NDBFS block's OM_SYNC flag is intended to make sure
        that all FSWRITEREQ signals used for a given file are
        synchronized, but was ignored by platforms that do not support
        O_SYNC, meaning that this feature did not behave properly on
        those platforms. Now the synchronization flag is used on those
        platforms that do not support O_SYNC. (Bug #76975, Bug
        #21049554)

On Behalf of MySQL/Oracle Release Engineering Team,
Surabhi Bhat