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
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.
Functionality Added or Changed
Added the ndb_mgm client command
DUMP 8011, which dumps all subscribers to the
cluster log. See
DUMP 8011, for more
The failure of a master node could lead to subsequent failures in local checkpointing. (Bug #32160)
High numbers of API nodes on a slow or congested network could cause connection negotiation to time out prematurely, leading to the following issues:
Excessive CPU usage
Partially connected API nodes
A restart of the cluster failed when more than 1 REDO phase was in use. (Bug #22696)
A local checkpoint could sometimes be started before the previous LCP was restorable from a global checkpoint. (Bug #32519)
Replication; Cluster Replication:
Where a table being replicated had a
BLOB column, an
UPDATE on the master that did not
refer explicitly to this column in the
clause stopped the SQL thread on the slave with Error
in Write_rows event: row application failed. Got error 4288
'Blob handle for column not available' from
Cluster Replication: Under certain conditions, the slave stopped processing relay logs. This resulted in the logs never being cleared and the slave eventually running out of disk space. (Bug #31958)