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.22, 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.22 (5.5.46-ndb-7.2.22) (2015-10-19)
MySQL Cluster NDB 7.2.22 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.46 (see Changes in MySQL 5.5.46 (2015-09-30)
(http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-46.html)).
Bugs Fixed
* Backup block states were reported incorrectly during
backups. (Bug #21360188)
References: See also Bug #20204854, Bug #21372136.
* When a data node is known to have been alive by other
nodes in the cluster at a given global checkpoint, but
its sysfile reports a lower GCI, the higher GCI is used
to determine which global checkpoint the data node can
recreate. This caused problems when the data node being
started had a clean file system (GCI = 0), or when it was
more than more global checkpoint behind the other nodes.
Now in such cases a higher GCI known by other nodes is
used only when it is at most one GCI ahead. (Bug
#19633824)
References: See also Bug #20334650, Bug #21899993. This
bug was introduced by Bug #29167.
* After restoring the database schema from backup using
ndb_restore, auto-discovery of restored tables in
transactions having multiple statements did not work
correctly, resulting in Deadlock found when trying to get
lock; try restarting transaction errors.
This issue was encountered both in the mysql client, as
well as when such transactions were executed by
application programs using Connector/J and possibly other
MySQL APIs.
Prior to upgrading, this issue can be worked around by
executing SELECT TABLE_NAME, TABLE_SCHEMA FROM
INFORMATION_SCHEMA.TABLES WHERE ENGINE = 'NDBCLUSTER' on
all SQL nodes following the restore operation, before
executing any other statements. (Bug #18075170)
* ndb_desc used with the --extra-partition-info and
--blob-info options failed when run against a table
containing one or more TINYBLOB. columns. (Bug #14695968)
* Cluster API: The internal value representing the latest
global checkpoint was not always updated when a completed
epoch of event buffers was inserted into the event queue.
This caused subsequent calls to Ndb::pollEvents() and
pollEvents2() to fail when trying to obtain the correct
GCI for the events available in the event buffers. This
could also result in later calls to nextEvent() or
nextEvent2() seeing events that had not yet been
discovered. (Bug #78129, Bug #21651536)
* Cluster API: While executing dropEvent(), if the
coordinator DBDICT failed after the subscription manager
(SUMA block) had removed all subscriptions but before the
coordinator had deleted the event from the system table,
the dropped event remained in the table, causing any
subsequent drop or create event with the same name to
fail with NDB error 1419 Subscription already dropped or
error 746 Event name already exists. This occurred even
when calling dropEvent() with a nonzero force argument.
Now in such cases, error 1419 is ignored, and DBDICT
deletes the event from the table. (Bug #21554676)
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/mysql
