This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.2 release.
MySQL Cluster NDB 6.2 no longer in development. MySQL Cluster NDB 6.2 is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.2 release, you should upgrade to the latest version of MySQL Cluster, which is available from http://dev.mysql.com/downloads/cluster/ .
Obtaining MySQL Cluster NDB 6.2. You can download the latest MySQL Cluster NDB 6.2 source code and binaries for supported platforms from http://dev.mysql.com/downloads/cluster/.
This Beta release 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.1 through MySQL 5.1.22 (see Changes in MySQL 5.1.22 (2007-09-24, Release Candidate)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
Important Note: MySQL Cluster NDB 6.2 and 6.3 source archives are now available in separate commercial and GPL versions. Due to licensing concerns, previous MySQL Cluster NDB 6.2 and 6.3 source archives were removed from the FTP site.
The output of the ndb_mgm client
STATUScommands now indicates when the cluster is in single user mode. (Bug #27999)
In a cluster running in diskless mode and with arbitration disabled, the failure of a data node during an insert operation caused other data node to fail. (Bug #31980)
An insert or update with combined range and equality constraints failed when run against an
NDBtable with the error Got unknown error from NDB. An example of such a statement would be
UPDATE t1 SET b = 5 WHERE a IN (7,8) OR a >= 10;. (Bug #31874)
An error with an
sql/ha_ndbcluster.cccould potentially lead to an infinite loop in case of failure when working with
NDBtables. (Bug #31810)
NDBstorage engine code was not safe for strict-alias optimization in gcc 4.2.1. (Bug #31761)
Following an upgrade, ndb_mgmd failed with an ArbitrationError. (Bug #31690)
NDBmanagement client command
provided no output when
node_idwas the node ID of a management or API node. Now, when this occurs, the management client responds with
Node. (Bug #29485)
node_id: is not a data node
DELETEoperations after a data node had been shut down could lead to inconsistent data following a restart of the node. (Bug #26450)
UPDATE IGNOREcould sometimes fail on
NDBtables due to the use of unitialized data when checking for duplicate keys to be ignored. (Bug #25817)
Replication; Cluster Replication: A node failure during replication could lead to buckets out of order; now active subscribers are checked for, rather than empty buckets. (Bug #31701)
Cluster Replication: When the master mysqld crashed or was restarted, no
LOST_EVENTSentry was made in the binlog. (Bug #31484)
References: See also: Bug #21494.