Documentation Home
MySQL NDB Cluster 6.1 - 7.1 Release Notes
Download these Release Notes
PDF (US Ltr) - 3.0Mb
PDF (A4) - 3.0Mb

MySQL NDB Cluster 6.1 - 7.1 Release Notes  /  Changes in MySQL Cluster NDB 6.2  /  Changes in MySQL Cluster NDB 6.2.12 (5.1.23-ndb-6.2.12) (2008-02-12)

Changes in MySQL Cluster NDB 6.2.12 (5.1.23-ndb-6.2.12) (2008-02-12)

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

This 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.23 (see Changes in MySQL 5.1.23 (2008-01-29)).


Please refer to our bug database at for more details about the individual bugs fixed in this version.

Functionality Added or Changed

  • Beginning with this version, MySQL Cluster NDB 6.3.x releases once again include the InnoDB storage engine. To enable InnoDB, you must configure the build using --with-innodb.

Bugs Fixed

  • Upgrades of a cluster using while a DataMemory setting in excess of 16 GB caused data nodes to fail. (Bug #34378)

  • Performing many SQL statements on NDB tables while in autocommit mode caused a memory leak in mysqld. (Bug #34275)

  • In certain rare circumstances, a race condition could occur between an aborted insert and a delete leading a data node crash. (Bug #34260)

  • Multi-table updates using ordered indexes during handling of node failures could cause other data nodes to fail. (Bug #34216)

  • When configured with NDB support, MySQL failed to compile using gcc 4.3 on 64bit FreeBSD systems. (Bug #34169)

  • The failure of a DDL statement could sometimes lead to node failures when attempting to execute subsequent DDL statements. (Bug #34160)

  • Extremely long SELECT statements (where the text of the statement was in excess of 50000 characters) against NDB tables returned empty results. (Bug #34107)

  • Statements executing multiple inserts performed poorly on NDB tables having AUTO_INCREMENT columns. (Bug #33534)

  • The ndb_waiter utility polled ndb_mgmd excessively when obtaining the status of cluster data nodes. (Bug #32025)

    References: See also: Bug #32023.

  • Transaction atomicity was sometimes not preserved between reads and inserts under high loads. (Bug #31477)

  • Having tables with a great many columns could cause Cluster backups to fail. (Bug #30172)

  • Disk Data; Cluster Replication: Statements violating unique keys on Disk Data tables (such as attempting to insert NULL into a NOT NULL column) could cause data nodes to fail. When the statement was executed from the binary log, this could also result in failure of the slave cluster. (Bug #34118)

  • Disk Data: Updating in-memory columns of one or more rows of Disk Data table, followed by deletion of these rows and re-insertion of them, caused data node failures. (Bug #33619)

  • Cluster Replication: Setting --replicate-ignore-db=mysql caused the mysql.ndb_apply_status table not to be replicated, breaking Cluster Replication. (Bug #28170)