MySQL Cluster 7.5.3 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, Memcached
     and JavaScript/Node.js)

MySQL Cluster 7.5.3(Release Candidate), 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.5/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 Cluster NDB 7.5.3 (5.7.13-ndb-7.5.3) (2016-07-08,
Release Candidate)

    MySQL Cluster NDB 7.5.3 is a new release of MySQL Cluster
    7.5, based on MySQL Server 5.7 and including features in
    version 7.5 of the NDB
    (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html)
    storage engine, as well as fixing recently discovered bugs in
    previous MySQL Cluster releases.

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

    For an overview of changes made in MySQL Cluster NDB 7.5, see
    What is New in MySQL Cluster NDB 7.5
    (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is
-new.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html>).

    This release also incorporates all bugfixes and changes made
    in previous MySQL Cluster releases, as well as all bugfixes
    and feature changes which were added in mainline MySQL 5.7
    through MySQL 5.7.13 (see Changes in MySQL 5.7.13
    (2016-06-02)
    (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-13.h
tml <http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-13.html>)).


    Functionality Added or Changed

      * Important Change: It is now possible to set READ_BACKUP
        for an existing table online using an SQL statement such
        as ALTER TABLE ... ALGORITHM=INPLACE,
        COMMENT="NDB_TABLE=READ_BACKUP=1"
        (http://dev.mysql.com/doc/refman/5.7/en/alter-table-onlin
e-operations.html 
<http://dev.mysql.com/doc/refman/5.7/en/alter-table-online-operations.html>). 
See Setting NDB_TABLE options in
        table comments
        (http://dev.mysql.com/doc/refman/5.7/en/create-table-ndb-
table-comment-options.html 
<http://dev.mysql.com/doc/refman/5.7/en/create-table-ndb-table-comment-options.html>), 
for further information
        about the READ_BACKUP option. (Bug #80858, Bug #23001617)
        References: See also: Bug #18435416.

      * Added three new tables to the ndbinfo
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo.html>) 
information database to provide running
        information about locks and lock attempts in an active
        MySQL Cluster. These tables, with brief descriptions, are
        listed here:

           + cluster_locks
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-cluster-locks.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cluster-locks.html>): 
Current lock requests
             which are waiting for or holding locks; this
             information can be useful when investigating stalls
             and deadlocks. Analogous to cluster_operations.

           + locks_per_fragment
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-locks-per-fragment.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-locks-per-fragment.html>): 
Counts of lock
             claim requests, and their outcomes per fragment, as
             well as total time spent waiting for locks
             successfully and unsuccessfully. Analogous to
             operations_per_fragment
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-operations-per-fragment.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-operations-per-fragment.html>) 
and
             memory_per_fragment
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-memory-per-fragment.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-memory-per-fragment.html>).

           + server_locks
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-server-locks.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-server-locks.html>): 
Subset of cluster
             transactions---those running on the local mysqld,
             showing a connection ID per transaction. Analogous
             to server_operations
             (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluste
r-ndbinfo-server-operations.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-server-operations.html>).
        For more information, see The ndbinfo MySQL Cluster
        Information Database
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo.html>).

    Bugs Fixed

      * The ndbinfo
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo.html>) 
cpustat_1sec
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat-1sec.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat-1sec.html>) 
and cpustat_20sec
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat-20sec.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat-20sec.html>) 
tables did not provide any
        history information. (Bug #23520271)

      * During shutdown, the mysqld process could sometimes hang
        after logging NDB Util: Stop ... NDB Util: Wakeup. (Bug
        #23343739)
        References: See also: Bug #21098142.

      * During expansion or reduction of a hash table, allocating
        a new overflow page in the DBACC kernel block caused the
        data node to fail when it was out of index memory. This
        could sometimes occur after a large table had increased
        or decreased very rapidly in size. (Bug #23304519)
        References: This issue is a regression of: Bug #13436216.

      * Following a restart of the cluster, the first attempt to
        read from any of the ndbinfo
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo.html>) cpustat
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat.html>), 
cpustat_50ms
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat-50ms.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat-50ms.html>), 
cpustat_1sec
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat-1sec.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat-1sec.html>), 
or cpustat_20sec
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
info-cpustat-20sec.html 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbinfo-cpustat-20sec.html>) 
tables generated a warning to
        the effect that columns were missing from the table.
        Subsequently, the thread_sleeping and spin_time columns
        were found to be missing from each of these tables. (Bug
        #81681, Bug #23514557)
        References: See also: Bug #23305078.

      * Using a ThreadConfig
        (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndb
d-definition.html#ndbparam-ndbmtd-threadconfig 
<http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-ndbd-definition.html#ndbparam-ndbmtd-threadconfig>) 
parameter
        value with a trailing comma led to an assertion. (Bug
        #81588, Bug #23344374)

      * Cluster API: The scan lock takeover issued by
        NdbScanOperation::lockCurrentTuple()
        (http://dev.mysql.com/doc/ndbapi/en/ndb-ndbscanoperation-
methods.html#ndb-ndbscanoperation-lockcurrenttuple 
<http://dev.mysql.com/doc/ndbapi/en/ndb-ndbscanoperation-methods.html#ndb-ndbscanoperation-lockcurrenttuple>) 
did
        not set the operation type for the takeover operation.
        (Bug #23314028)      * Table indexes were listed in the output 
of ndb_desc in a
        nondeterministic order that could vary between platforms.
        Now these indexes are ordered by ID in the output. (Bug
        #81763, Bug #23547742)

Regards
-Sree