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.25, 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.25 (5.5.50-ndb-7.2.25) (2016-07-18)

MySQL Cluster NDB 7.2.25 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.50 (see Changes in MySQL 5.5.50
(2016-06-02)
(http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-50.html)).

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)

On behalf of Oracle MySQL RE team
Gipson Pulla

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