MySQL Cluster 7.2.26 has been released

[Piotr Obrzut]

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.26, 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.26 (5.5.53-ndb-7.2.26) (2016-10-18, General Availability)


   MySQL Cluster NDB 7.2.26 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.53
   (see Changes in MySQL 5.5.53 (Not yet released)
(http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-53.html)).

   Bugs Fixed

     * Several object constructors and similar functions in the
       NDB codebase did not always perform sanity checks when creating
       new instances. These checks are now performed under such
       circumstances. (Bug #77408, Bug #21286722)

On behalf of the Oracle MySQL RE Team
Piotr Obrzut