This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.2 release.
MySQL Cluster NDB 6.2 no longer in development. MySQL Cluster NDB 6.2 is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.2 release, you should upgrade to the latest version of MySQL Cluster, which is available from http://dev.mysql.com/downloads/cluster/ .
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 release incorporates all 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.23 (see Changes in MySQL 5.1.23 (2008-01-29)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
Important Change; Cluster API: Because
NDB_LE_MemoryUsage.page_size_kbshows memory page sizes in bytes rather than kilobytes, it has been renamed to
page_size_bytes. The name
page_size_kbis now deprecated and thus subject to removal in a future release, although it currently remains supported for reasons of backward compatibility. See The
Ndb_logevent_typeType, for more information about
NDB_LE_MemoryUsage. (Bug #30271)
High numbers of insert operations, delete operations, or both could cause
NDBerror 899 (Rowid already allocated) to occur unnecessarily. (Bug #34033)
A periodic failure to flush the send buffer by the
NDBTCP transporter could cause a unnecessary delay of 10 ms between operations. (Bug #34005)
A race condition could occur (very rarely) when the release of a GCI was followed by a data node failure. (Bug #33793)
Some tuple scans caused the wrong memory page to be accessed, leading to invalid results. This issue could affect both in-memory and Disk Data tables. (Bug #33739)
The server failed to reject properly the creation of an
NDBtable having an unindexed
AUTO_INCREMENTcolumn. (Bug #30417)
The Cluster backup process could not detect when there was no more disk space and instead continued to run until killed manually. Now the backup fails with an appropriate error when disk space is exhausted. (Bug #28647)
It was possible in
config.inito define cluster nodes having node IDs greater than the maximum permitted value. (Bug #28298)
Cluster Replication: ndb_restore -e restored excessively large values to the
epochcolumn when restoring to a MySQL Cluster version supporting Micro-GCPs from an older version that did not support these.
A workaround when restoring to MySQL Cluster releases supporting micro-GCPs previous to MySQL Cluster NDB 6.3.8 is to perform a 32-bit shift on the
epochcolumn values to reduce them to their proper size. (Bug #33406)
Cluster API: Transactions containing inserts or reads would hang during
NdbTransaction::execute()calls made from NDB API applications built against a MySQL Cluster version that did not support micro-GCPs accessing a later version that supported micro-GCPs. This issue was observed while upgrading from MySQL Cluster NDB 6.1.23 to MySQL Cluster NDB 6.2.10 when the API application built against the earlier version attempted to access a data node already running the later version, even after disabling micro-GCPs by setting
TimeBetweenEpochsequal to 0. (Bug #33895)
Cluster API: When reading a
NdbOperation::getValue(), 12 bytes were written to the buffer rather than the expected 8 bytes. (Bug #33750)