MySQL Forums
Forum List  »  Announcements

MySQL Cluster 7.3.14 has been released
Posted by: Balasubramanian Kandasamy
Date: July 18, 2016 04:29AM


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.14, 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.3/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.3.14 (5.6.31-ndb-7.3.14) (2016-07-18)

   MySQL Cluster NDB 7.3.14 is a new release of MySQL 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 MySQL Cluster releases.

   Obtaining MySQL Cluster NDB 7.3.  MySQL Cluster NDB 7.3
   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.3, see
   What is New in MySQL Cluster NDB 7.3
   (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is
   -new-7-3.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.6
   through MySQL 5.6.31 (see Changes in MySQL 5.6.31
   (2016-06-02)
   (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-31.h
   tml)).

     * Functionality Added or Changed

     * Bugs Fixed

   Functionality Added or Changed

     * ClusterJ: To make it easier for ClusterJ to handle fatal
       errors that require the SessionFactory to be closed, a
       new public method in the SessionFactory interface,
       getConnectionPoolSessionCounts()
       (http://dev.mysql.com/doc/ndbapi/en/mccj-clusterj-session
       factory.html#mccj-clusterj-sessionfactory-getconnectionpo
       olsessioncounts), has been created. When it returns zeros
       for all pooled connections, it means all sessions have
       been closed, at which point the SessionFactory can be
       closed and reopened. See Reconnecting to a MySQL Cluster
       (http://dev.mysql.com/doc/ndbapi/en/mccj-using-clusterj-s
       tart.html#mccj-using-clusterj-reconnect) for more detail.
       (Bug #22353594)

   Bugs Fixed

     * Incompatible Change: When the data nodes are only
       partially connected to the API nodes, a node used for a
       pushdown join may get its request from a transaction
       coordinator on a different node, without (yet) being
       connected to the API node itself. In such cases, the
       NodeInfo object for the requesting API node contained no
       valid info about the software version of the API node,
       which caused the DBSPJ block to assume (incorrectly) when
       aborting to assume that the API node used NDB version
       7.2.4 or earlier, requiring the use of a backward
       compatability mode to be used during query abort which
       sent a node failure error instead of the real error
       causing the abort.
       Now, whenever this situation occurs, it is assumed that,
       if the NDB software version is not yet available, the API
       node version is greater than 7.2.4. (Bug #23049170)

     * During a node restart, re-creation of internal triggers
       used for verifying the referential integrity of foreign
       keys was not reliable, because it was possible that not
       all distributed TC and LDM instances agreed on all
       trigger identities. To fix this problem, an extra step is
       added to the node restart sequence, during which the
       trigger identities are determined by querying the current
       master node. (Bug #23068914)
       References: See also: Bug #23221573.

     * Following the forced shutdown of one of the 2 data nodes
       in a cluster where NoOfReplicas=2, the other data node
       shut down as well, due to arbitration failure. (Bug
       #23006431)

     * Cluster API: Deletion of Ndb objects used a
       dispoportionately high amount of CPU. (Bug #22986823)


On behalf of the MySQL Release Team,
Balasubramanian Kandasamy


Options: ReplyQuote


Subject
Views
Written By
Posted
MySQL Cluster 7.3.14 has been released
1403
July 18, 2016 04:29AM


Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.