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.5 Changes in MySQL Cluster NDB 6.1 :: 17.7.5.20 Changes in MySQL Cluster NDB 6.1.4 (5.1.15-ndb-6.1.4) (09 March 2007)
17.7.5.21 Changes in MySQL Cluster NDB 6.1.3 (5.1.15-ndb-6.1.3) (25 February 2007) »
Section Navigation      [Toggle]

17.7.5.20. Changes in MySQL Cluster NDB 6.1.4 (5.1.15-ndb-6.1.4) (09 March 2007)

This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.1 release.

MySQL Cluster NDB 6.1 no longer in development.  MySQL Cluster NDB 6.1 (formerly known as “MySQL Cluster Carrier Grade Edition 6.1.x”) is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.1 release, you should consider upgrading to MySQL Cluster NDB 6.2 or 6.3.

This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 6.1 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.15 (see Section C.1.37, “Changes in MySQL 5.1.15 (25 January 2007)”).

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:

  • An ndb_wait_connected system variable has been added for mysqld. It causes mysqld wait a specified amount of time to be connected to the cluster before accepting client connections. For more information, see Section 17.3.4.3, “MySQL Cluster System Variables”.

  • Cluster API: It is now possible to specify the transaction coordinator when starting a transaction. See Ndb::startTransaction(), for more information.

  • Cluster API: It is now possible to iterate over all existing NDB objects using three new methods of the Ndb_cluster_connection class:

    • lock_ndb_objects()

    • get_next_ndb_object()

    • unlock_ndb_objects()

    For more information about these methods and their use, see ndb_cluster_connection::get_next_ndb_object(), in the MySQL Cluster API Guide.

  • Data node memory allocation has been improved. On 32-bit platforms, it should now be possible to use close to 3GB RAM for IndexMemory and DataMemory combined.

Bugs fixed:

  • Using only the --print_data option (and no other options) with ndb_restore caused ndb_restore to fail. (Bug#26741)

    This regression was introduced by Bug#14612.

  • An inadvertent use of unaligned data caused ndb_restore to fail on some 64-bit platforms, including Sparc and Itanium-2. (Bug#26739)

  • Assigning a node ID greater than 63 to an SQL node caused an out of bounds error in mysqld. It should now be possible to assign to SQL nodes node IDs up to 255. (Bug#26663)