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.27, 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

Changes in MySQL NDB Cluster 7.2.27 (5.5.54-ndb-7.2.27) (2017-01-17)

   MySQL NDB Cluster 7.2.27 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

   This release also incorporates all bugfixes and changes made
   in previous NDB Cluster releases, as well as all bugfixes and
   feature changes which were added in mainline MySQL 5.5
   through MySQL 5.5.54 (see Changes in MySQL 5.5.54
   (2016-12-12, General availability)

   Bugs Fixed

     * A number of potential buffer overflow issues were found
       and fixed in the NDB codebase. (Bug #25260091)
       References: See also: Bug #23152979.

     * ndb_restore did not restore tables having more than 341
       columns correctly. This was due to the fact that the
       buffer used to hold table metadata read from .ctl files
       was of insufficient size, so that only part of the table
       descriptor could be read from it in such cases. This
       issue is fixed by increasing the size of the buffer used
       by ndb_restore for file reads. (Bug #25182956)

On Behalf of MySQL Release Engineering Team,
Gipson Pulla

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to