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.15, 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.15 (5.6.34-ndb-7.3.15) (2016-10-18)

MySQL Cluster NDB 7.3.15 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.34 (see Changes in MySQL 5.6.34
(2016-10-12, General Availability)
(http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-34.html)).

* Functionality Added or Changed

* Bugs Fixed

Functionality Added or Changed

* ClusterJ: To help applications handle database errors
better, a number of new features have been added to the
ClusterJDatastoreException class:

+ A new method, getCode(), returns code from the
NdbError object.

+ A new method, getMysqlCode(), returns mysql_code
from the NdbError object.

+ A new subclass,
ClusterJDatastoreException.Classification, gives
users the ability to decode the result from
getClassification(). The method
Classification.toString() gives the name of the
error classification as listed in NDB Error
Classifications
(http://dev.mysql.com/doc/ndbapi/en/ndb-error-classifications.html).
(Bug #22353594)

Bugs Fixed

* Removed an invalid assertion to the effect that all
cascading child scans are closed at the time API
connection records are released following an abort of the
main transaction. The assertion was invalid because
closing of scans in such cases is by design asynchronous
with respect to the main transaction, which means that
subscans may well take some time to close after the main
transaction is closed. (Bug #23709284)

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

* When a data node has insufficient redo buffer during a
system restart, it does not participate in the restart
until after the other nodes have started. After this, it
performs a takeover of its fragments from the nodes in
its node group that have already started; during this
time, the cluster is already running and user activity is
possible, including DML and DDL operations.
During a system restart, table creation is handled
differently in the DIH kernel block than normally, as
this creation actually consists of reloading table
definition data from disk on the master node. Thus, DIH
assumed that any table creation that occurred before all
nodes had restarted must be related to the restart and
thus always on the master node. However, during the
takeover, table creation can occur on non-master nodes
due to user activity; when this happened, the cluster
underwent a forced shutdown.
Now an extra check is made during system restarts to
detect in such cases whether the executing node is the
master node, and use that information to determine
whether the table creation is part of the restart proper,
or is taking place during a subsequent takeover. (Bug
#23028418)

* 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)

* Cluster API: Reuse of transaction IDs could occur when
Ndb objects were created and deleted concurrently. As
part of this fix, the NDB API methods lock_ndb_objects()
and unlock_ndb_objects are now declared as const. (Bug
#23709232)


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql