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.4 Changes in MySQL Cluster NDB 6.2 :: 17.7.4.20 Changes in MySQL Cluster NDB 6.2.0 (5.1.16-ndb-6.2.0) (03 March 2007 Beta)
17.7.5 Changes in MySQL Cluster NDB 6.1 »
Section Navigation      [Toggle]

17.7.4.20. Changes in MySQL Cluster NDB 6.2.0 (5.1.16-ndb-6.2.0) (03 March 2007 Beta)

This is the first MySQL Cluster NDB 6.2 development release, based on version 6.2 of the NDBCLUSTER storage engine.

Obtaining MySQL Cluster NDB 6.2.  You can download the latest MySQL Cluster NDB 6.2 source code and binaries for supported platforms from http://dev.mysql.com/downloads/select.php?id=14.

This Beta release incorporates 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.16 (see Section C.1.36, “Changes in MySQL 5.1.16 (26 February 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: The Ndb::startTransaction() method now provides an alternative interface for starting a transaction. See Ndb::startTransaction(), for more information.

  • Cluster API: Methods were added to the Ndb_cluster_connection class to faciliate iterating over existing NDB objects. See ndb_cluster_connection::get_next_ndb_object(), for more information.

  • It is now possible to disable arbitration by setting ArbitrationRank equal to 0 on all nodes.

  • A new TcpBind_INADDR_ANY configuration parameter allows data nodes node to bind INADDR_ANY instead of a host name or IP address in the config.ini file.

  • Memory allocation has been improved on 32-bit architectures that enables using close to 3GB for DataMemory and IndexMemory combined.