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

Enjoy !

Changes in MySQL NDB Cluster 7.3.18 (5.6.37-ndb-7.3.18) (2017-07-18, General Availability)

   MySQL NDB Cluster 7.3.18 is a new release of NDB Cluster,
   based on MySQL Server 5.6 and including features from version
   7.3 of the NDB storage engine, as well as fixing a number of
   recently discovered bugs in previous NDB Cluster releases.

   Obtaining MySQL NDB Cluster 7.3.  MySQL NDB Cluster 7.3
   source code and binaries can be obtained from

   For an overview of changes made in MySQL NDB Cluster 7.3, see
   What is New in NDB Cluster 7.3


   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.6
   through MySQL 5.6.37 (see Changes in MySQL 5.6.37
   (2017-07-17, General Availability)

   Functionality Added or Changed

     * Important Change; MySQL NDB ClusterJ: The ClusterJPA
       plugin for OpenJPA is no longer supported by NDB Cluster,
       and has been removed from the distribution. (Bug

   Bugs Fixed

     * NDB Replication: Added a check to stop an NDB replication
       slave when configuration as a multi-threaded slave is
       detected (for example, if slave_parallel_workers is set
       to a nonzero value). (Bug #21074209)

     * Backup .log files contained log entries for one or more
       extra fragments, due to an issue with filtering out
       changes logged by other nodes in the same node group.
       This resulted in a larger .log file and thus use of more
       resources than necessary; it could also cause problems
       when restoring, since backups from different nodes could
       interfere with one another while the log was being
       applied. (Bug #25891014)

     * Error 240 is raised when there is a mismatch between
       foreign key trigger columns and the values supplied to
       them during trigger execution, but had no error message
       indicating the source of the problem. (Bug #23141739)
       References: See also: Bug #23068914, Bug #85857.

     * ALTER TABLE .. MAX_ROWS=0 can now be performed only by
       using a copying ALTER TABLE statement. Resetting MAX_ROWS
       to 0 can no longer be performed using ALGORITHM=INPLACE
       or the ONLINE keyword. (Bug #21960004)

     * When compiling the NDB kernel with gcc version 6.0.0 or
       later, it is now built using -flifetime-dse=1. (Bug
       #85381, Bug #25690926)

On Behalf of the MySQL/Oracle Release Engineering Team,
Kent Boortz & Hery Ramilison

MySQL General Mailing List
For list archives:
To unsubscribe:

Reply via email to