This release incorporates new features in the
NDB storage engine and fixes
recently discovered bugs in previous MySQL Cluster NDB 7.0
Obtaining MySQL Cluster NDB 7.0. The latest MySQL Cluster NDB 7.0 binaries for supported platforms can be obtained from http://dev.mysql.com/downloads/cluster/. Source code for the latest MySQL Cluster NDB 7.0 release can be obtained from the same location. You can also access the MySQL Cluster NDB 7.0 development source tree at https://code.launchpad.net/~mysql/mysql-server/mysql-cluster-7.0.
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.1 through MySQL 5.1.56 (see Changes in MySQL 5.1.56 (2011-03-01)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
MinFreePctdata node configuration parameter, which specifies a percentage of data node resources to hold in reserve for restarts. The resources monitored are
IndexMemory, and any per-table
MAX_ROWSsettings (see CREATE TABLE Syntax). The default value of
MinFreePctis 5, which means that 5% from each these resources is now set aside for restarts. (Bug #13436216)
Because the log event buffer used internally by data nodes was circular, periodic events such as statistics events caused it to be overwritten too quickly. Now the buffer is partitioned by log event category, and its default size has been increased from 4K to 8K. (Bug #13394771)
BatchByteSizeconfiguration parameters, used to control the maximum sizes of result batches, are defined as integers. However, the values used to store these were incorrectly interpreted as numbers of bytes in the NDB kernel. This caused the
DBLQHkernel block to fail to detect when the specified
BatchByteSizewas consumed. (Bug #13355055)
Previously, forcing simultaneously the shutdown of multiple data nodes using
SHUTDOWN -Fin 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 TABLEcould cause data node processes (ndbmtd) to fail. (Bug #13447705)