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.26 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 NDB Cluster 7.3.26 (5.6.45-ndb-7.3.26) (2019-07-23, General Availability)
MySQL NDB Cluster 7.3.26 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
https://dev.mysql.com/downloads/cluster/.
For an overview of changes made in MySQL NDB Cluster 7.3, see
What is New in NDB Cluster 7.3
(https://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-i
s-new-7-3.html).
This release also incorporates all bug fixes and changes made
in previous NDB Cluster releases, as well as all bug fixes
and feature changes which were added in mainline MySQL 5.6
through MySQL 5.6.45 (see Changes in MySQL 5.6.45 (2019-07-23, General Availability)
(https://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-45.html)).
Bugs Fixed
* The requestInfo fields for the long and short forms of
the LQHKEYREQ signal had diffferent definitions; bits
used for the key length in the short version were reused
for flags in the long version, since the key length is
implicit in the section length of the long version of the
dignal but it was possible for long LQHKEYREQ signals to
contain a keylength in these same bits, which could be
misinterpreted by the receiving local query handler,
potentially leading to errors. Checks have now been
implemented to make sure that this no longer happens.
(Bug #29820838)
* ndb_restore --restore-epoch incorrectly reported the stop
GCP as 1 less than the actual position. (Bug #29343655)