Skip navigation links
MySQL 5.1 Reference Manual :: 17 MySQL Cluster NDB 6.X/7.X :: 17.7 Changes in MySQL Cluster NDB 6.X and 7.X :: 17.7.2 Changes in MySQL Cluster NDB 7.0 :: 17.7.2.23 Changes in MySQL Cluster NDB 6.4.0 (5.1.30-ndb-6.4.0) (22 December 2008 Beta)
17.7.3 Changes in MySQL Cluster NDB 6.3 »
Section Navigation      [Toggle]

17.7.2.23. Changes in MySQL Cluster NDB 6.4.0 (5.1.30-ndb-6.4.0) (22 December 2008 Beta)

This is a new Beta development release, incorporating new features in the NDBCLUSTER storage engine and fixing recently discovered bugs in previous MySQL Cluster releases.

Obtaining MySQL Cluster NDB 6.4.0.  MySQL Cluster NDB 6.4.0 is a source-only release. You can obtain the source code from ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/mysql-5.1.30-ndb-6.4.0/.

This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 6.1, 6.2, and 6.3 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.30 (see Section C.1.22, “Changes in MySQL 5.1.30 (14 November 2008 General Availability)”).

Note

This Beta release, as any other pre-production release, should not be installed on production level systems or systems with critical data. 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:

  • API nodes disconnected too agressively from cluster when data nodes were being restarted. This could sometimes lead to the API node being unable to access the cluster at all during a rolling restart. (Bug#41462)

  • When long signal buffer exhaustion in the ndbd process resulted in a signal being dropped, the usual handling mechanism did not take fragmented signals into account. This could result in a crash of the data node because the fragmented signal handling mechanism was not able to work with the missing fragments. (Bug#39235)

  • The failure of a master node during a DDL operation caused the cluster to be unavailable for further DDL operations until it was restarted; failures of nonmaster nodes during DLL operations caused the cluster to become completely inaccessible. (Bug#36718)

  • Status messages shown in the management client when restarting a management node were inappropriate and misleading. Now, when restarting a management node, the messages displayed are as follows, where node_id is the management node's node ID: 

    ndb_mgm> node_id RESTART
Shutting down MGM node node_id for restart
Node node_id is being restarted

ndb_mgm>

    (Bug#29275)

  • A data node failure when NoOfReplicas was greater than 2 caused all cluster SQL nodes to crash. (Bug#18621)

  • Partitioning: A query on a user-partitioned table caused MySQL to crash, where the query had the following characteristics:

    • The query's WHERE clause referenced an indexed column that was also in the partitioning key.

    • The query's WHERE clause included a value found in the partition.

    • The query's WHERE clause used the < or <> operators to compare with the indexed column's value with a constant.

    • The query used an ORDER BY clause, and the same indexed column was used in the ORDER BY clause.

    • The ORDER BY clause used an explcit or implicit ASC sort priority.

    Two examples of such a query are given here, where a represents an indexed column used in the table's partitioning key: 

    1. SELECT * FROM table WHERE a < constant ORDER BY a;


    2. SELECT * FROM table WHERE a <> constant ORDER BY a;

    (Bug#40954)

    This regression was introduced by Bug#30573, Bug#33257, Bug#33555.