MySQL Cluster 7.2.24 has been released

[Prashant Tekriwal]

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.24, 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 Cluster NDB 7.2.24 (5.5.48-ndb-7.2.24) (2016-04-19)

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

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

   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.5
   through MySQL 5.5.48 (see Changes in MySQL 5.5.48 (2016-02-05)(
   http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-48.html)).

   Bugs Fixed

     * Restoration of metadata with ndb_restore -m occasionally
       failed with the error message Failed to create index...
       when creating a unique index. While diagnosing this
       problem, it was found that the internal error
       PREPARE_SEIZE_ERROR (a temporary error) was reported as
       an unknown error. Now in such cases, ndb_restore retries
       the creation of the unique index, and PREPARE_SEIZE_ERROR
       is reported as NDB Error 748 Busy during read of event
       table. (Bug #21178339)
       References: See also Bug #22989944.