This release incorporates new features in the
NDB storage engine and fixes
recently discovered bugs in MySQL Cluster NDB 7.0.17.
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.47 (see Changes in MySQL 5.1.47 (2010-05-06)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
Important Change: More finely grained control over restart-on-failure behavior is provided with two new data node configuration parameters
MaxStartFailRetrieslimits the total number of retries made before giving up on starting the data node;
StartFailRetryDelaysets the number of seconds between retry attempts.
These parameters are used only if
StopOnErroris set to 0.
For more information, see Defining MySQL Cluster Data Nodes. (Bug #54341)
ndb_restore always reported 0 for the
GCPStop(end point of the backup). Now it provides useful binary log position and epoch information. (Bug #56298)
LockExecuteThreadToCPUconfiguration parameter was not handled correctly for CPU ID values greater than 255. (Bug #56185)
Following a failure of the master data node, the new master sometimes experienced a race condition which caused the node to terminate with a GcpStop error. (Bug #56044)
Trying to create a table having a
DEFAULT ''failed with the error Illegal null attribute. (An empty default is permitted and ignored by
NDBshould do the same.) (Bug #55121)
--nodaemonlogged to the console in addition to the configured log destination. (Bug #54779)
The warning MaxNoOfExecutionThreads (
#) > LockExecuteThreadToCPU count (
#), this could cause contention could be logged when running ndbd, even though the condition described can occur only when using ndbmtd. (Bug #54342)
Startup messages previously written by ndb_mgmd to
stdoutare now written to the cluster log instead when
LogDestinationis set. (Bug #47595)
The graceful shutdown of a data node could sometimes cause transactions to be aborted unnecessarily. (Bug #18538)
References: See also: Bug #55641.
Cluster Replication: The graceful shutdown of a data node in the master cluster could sometimes cause rows to be skipped when writing transactions to the binary log, leading to an inconsistent slave cluster. (Bug #55641)
References: See also: Bug #18538.
Cluster Replication: Specifying the
--expire_logs_daysoption when there were old binary logs to delete caused SQL nodes to crash on startup. (Bug #41751)