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.28 (5.1.56-ndb-7.0.28) (2011-11-23)
Changes in MySQL Cluster NDB 7.0.27 (5.1.56-ndb-7.0.27) (Not released) »
Section Navigation      [Toggle]

Changes in MySQL Cluster NDB 7.0.28 (5.1.56-ndb-7.0.28) (2011-11-23)

This release incorporates new features in the NDBCLUSTER storage engine and fixes recently discovered bugs in previous MySQL Cluster NDB 7.0 releases.

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.56 (see Changes in MySQL 5.1.56 (2011-03-01)).

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

  • Introduced the CrashOnCorruptedTuple data node configuration parameter. When enabled, this parameter causes data nodes to handle corrupted tuples in a fail-fast manner—in other words, whenever the data node detects a corrupted tuple, it forcibly shuts down if CrashOnCorruptedTuple is enabled. For backward compatibility, this parameter is disabled by default. (Bug #12598636)

Bugs Fixed

  • When a failure of multiple data nodes during a local checkpoint (LCP) that took a long time to complete included the node designated as master, any new data nodes attempting to start before all ongoing LCPs were completed later crashed. This was due to the fact that node takeover by the new master cannot be completed until there are no pending local checkpoints. Long-running LCPs such as those which triggered this issue can occur when fragment sizes are sufficiently large (see MySQL Cluster Nodes, Node Groups, Replicas, and Partitions, for more information). Now in such cases, data nodes (other than the new master) are kept from restarting until the takeover is complete. (Bug #13323589)

  • When deleting from multiple tables using a unique key in the WHERE condition, the wrong rows were deleted. In addition, UPDATE triggers failed when rows were changed by deleting from or updating multiple tables. (Bug #12718336, Bug #61705, Bug #12728221)

  • A SubscriberNodeIdUndefined error was previously unhandled, resulting in a data node crash, but is now handled by NDB Error 1429, Subscriber node undefined in SubStartReq. (Bug #12598496)

  • Shutting down a mysqld while under load caused the spurious error messages Opening ndb_binlog_index: killed and Unable to lock table ndb_binlog_index to be written in the cluster log. (Bug #11930428)

  • Cluster Replication: The mysqlbinlog --database option generated table mapping errors when used with NDB tables, unless the binary log was generated using --log-bin-use-v1-row-events=0. (Bug #13067813)

  • Cluster Replication: Replication of NDB tables having more columns on the slave than on the master did not always work correctly when any of the extra columns were NOT NULL, did not have a default value, or both. (Bug #11755904, Bug #47742)

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