This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.1 release.
MySQL Cluster NDB 6.1 no longer in development. MySQL Cluster NDB 6.1 (formerly known as “MySQL Cluster Carrier Grade Edition 6.1.x”) is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.1 release, you should upgrade to the latest version of MySQL Cluster, which is available from http://dev.mysql.com/downloads/cluster/ .
This Beta release incorporates all bugfixes and changes made in the previous MySQL Cluster NDB 6.1 release, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.15 (see Changes in MySQL 5.1.15 (2007-01-25)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
A single cluster can now support up to 255 API nodes, including MySQL servers acting as SQL nodes. See Issues Exclusive to MySQL Cluster, for more information.
A memory leak could cause problems during a node or cluster shutdown or failure. (Bug #25997)
Disk Data; Cluster API: A delete and a read performed in the same operation could cause one or more data nodes to crash. This could occur when the operation affected more than 5 columns concurrently, or when one or more of the columns was of the
VARCHARtype and was stored on disk. (Bug #25794)
An element could sometimes be inserted twice into the hash table, causing a data node to crash. (Bug #25286)