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.3 (5.5.17-ndb-7.2.3) (Not released)

Changes in MySQL Cluster NDB 7.2.3 (5.5.17-ndb-7.2.3) (Not released)

MySQL Cluster NDB 7.2.3 is a new development preview release of MySQL Cluster, incorporating new features in the NDB storage engine for testing and user feedback.

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.17 (see Changes in MySQL 5.5.17 (2011-10-19)).

Functionality Added or Changed

  • Added the ThreadConfig data node configuration parameter to enable control of multiple threads and CPUs when using ndbmtd, by assigning threads of one or more specified types to execute on one or more CPUs. This can provide more precise and flexible control over multiple threads than can be obtained using the LockExecuteThreadToCPU parameter. (Bug #11795581)

Bugs Fixed

  • Important Change; Cluster Replication: A unique key constraint violation caused NDB slaves to stop rather than to continue when the slave_exec_mode was IDEMPOTENT. In such cases, NDB now behaves as other MySQL storage engines do when in IDEMPOTENT mode. (Bug #11756310)

  • Added the MinFreePct data node configuration parameter, which specifies a percentage of data node resources to hold in reserve for restarts. The resources monitored are DataMemory, IndexMemory, and any per-table MAX_ROWS settings (see CREATE TABLE Syntax). The default value of MinFreePct is 5, which means that 5% from each these resources is now set aside for restarts. (Bug #13436216)

  • Issuing TRUNCATE TABLE on mysql.user,, mysql.db, mysql.tables_priv, mysql.proxies_priv, or mysql.procs_priv, when these tables had been converted to MySQL Cluster distributed grant tables, caused mysqld to crash. (Bug #13346955)

  • Restarting an SQL node configured for distributed grants could sometimes result in a crash. (Bug #13340819)

  • Previously, forcing simultaneously the shutdown of multiple data nodes using SHUTDOWN -F in the ndb_mgm management client could cause the entire cluster to fail. Now in such cases, any such nodes are forced to abort immediately. (Bug #12928429)

  • Cluster Replication: With many SQL nodes, all writing binary logs, connected to a MySQL Cluster, RENAME TABLE could cause data node processes (ndbmtd) to fail. (Bug #13447705)