Documentation Home
MySQL Cluster 7.2 Release Notes
Download these Release Notes
PDF (US Ltr) - 0.5Mb
PDF (A4) - 0.5Mb
EPUB - 134.1Kb

MySQL Cluster 7.2 Release Notes  /  Changes in MySQL Cluster NDB 7.2  /  Changes in MySQL Cluster NDB 7.2.13 (5.5.31-ndb-7.2.13) (2013-06-14)

Changes in MySQL Cluster NDB 7.2.13 (5.5.31-ndb-7.2.13) (2013-06-14)

MySQL Cluster NDB 7.2.13 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

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.31 (see Changes in MySQL 5.5.31 (2013-04-18)).

Functionality Added or Changed

  • Cluster API: Added DUMP code 2514, which provides information about counts of transaction objects per API node. For more information, see DUMP 2514. See also Commands in the MySQL Cluster Management Client. (Bug #15878085)

  • When ndb_restore fails to find a table, it now includes in the error output an NDB API error code giving the reason for the failure. (Bug #16329067)

Bugs Fixed

  • Incompatible Change; Cluster Replication: The default value for the binlog_format system variable when the NDB storage engine is enabled is now MIXED. If NDB is not enabled, the default binary logging format is STATEMENT, as in the standard MySQL Server. (Bug #16417224)

  • The NDB Error-Reporting Utility (ndb_error_reporter) failed to include the cluster nodes' log files in the archive it produced when the FILE option was set for the parameter LogDestination. (Bug #16765651)

    References: See also: Bug #11752792, Bug #44082.

  • A WHERE condition that contained a boolean test of the result of an IN subselect was not evaluated correctly. (Bug #16678033)

  • In some cases a data node could stop with an exit code but no error message other than (null) was logged. (This could occur when using ndbd or ndbmtd for the data node process.) Now in such cases the appropriate error message is used instead (see ndbd Error Messages). (Bug #16614114)

  • mysql_upgrade failed when run on an SQL node where distributed privileges were in use. (Bug #16226274)

  • Improved handling of lagging row change event subscribers by setting size of the GCP pool to the value of MaxBufferedEpochs. This fix also introduces a new MaxBufferedEpochBytes data node configuration parameter, which makes it possible to set a total number of bytes per node to be reserved for buffering epochs. In addition, a new DUMP code (8013) has been added which causes a list a lagging subscribers for each node to be printed to the cluster log (see DUMP 8013). (Bug #16203623)

  • Purging the binary logs could sometimes cause mysqld to crash. (Bug #15854719)

  • An error message in src/mgmsrv/MgmtSrvr.cpp was corrected. (Bug #14548052, Bug #66518)

  • The help text for ndb_select_count did not include any information about using table names. (Bug #11755737, Bug #47551)