This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.2 release.
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/cluster/.
This Beta release incorporates all bugfixes and changes made in previous MySQL Cluster NDB 6.2 releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.1 through MySQL 5.1.22 (see Changes in MySQL 5.1.22 (2007-09-24, Release Candidate)).
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
A new configuration parameter
enables a timeout to be set for time between epochs.
Additional checks were implemented to catch unsupported online
ALTER TABLE operations. Currently
it is not possible to reorder columns or to change the storage
engine used for a table using online
Some redundant checks made during online creation of indexes were removed.
It was possible in some cases for a node group to be “lost” due to missed local checkpoints following a system restart. (Bug #31525)
A node failure during a local checkpoint could lead to a subsequent failure of the cluster during a system restart. (Bug #31257)
--help did not
display any information about the
NDB tables having names containing
nonalphanumeric characters (such as
$”) were not discovered
A cluster restart could sometimes fail due to an issue with table IDs. (Bug #30975)
The cluster log was formatted inconsistently and contained extraneous newline characters. (Bug #25064)
Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug #30379)
In some cases, the cluster managment server logged entries multiple times following a restart of ndb_mgmd. (Bug #29565)
The mysqld_safe script contained a syntax error. (Bug #30624)
ALTER operations involving a column
whose data type has an implicit default value left behind
.frm files, causing subsequent
DROP DATABASE statements to fail.
Transactions were committed prematurely when
SET autocommit = 0 were