Skip navigation links
MySQL Cluster 6.1 - 7.1 Release Notes :: Changes in MySQL Cluster NDB 7.0 :: Changes in MySQL Cluster NDB 7.0.18 (5.1.47-ndb-7.0.18) (2010-09-03)
Changes in MySQL Cluster NDB 7.0.17 (5.1.47-ndb-7.0.17) (2010-08-16) »
Section Navigation      [Toggle]

Changes in MySQL Cluster NDB 7.0.18 (5.1.47-ndb-7.0.18) (2010-09-03)

This release incorporates new features in the NDBCLUSTER 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 NDB 6.1, 6.2, 6.3, and 7.0 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)).

Note

Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.

Functionality Added or Changed

Bugs Fixed

  • 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)

  • The LockExecuteThreadToCPU configuration parameter was not handled correctly for CPU ID values greater than 255. (Bug #56185)

  • Trying to create a table having a BLOB or TEXT column with DEFAULT '' failed with the error Illegal null attribute. (An empty default is permitted and ignored by MyISAM; NDB should do the same.) (Bug #55121)

  • 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)

  • ndb_mgmd --nodaemon logged 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 stdout are now written to the cluster log instead when LogDestination is 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_days option when there were old binary logs to delete caused SQL nodes to crash on startup. (Bug #41751)

Copyright © 1997, 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices