This is a bugfix release, fixing recently discovered bugs in the previous MySQL Cluster NDB 6.3 release.
MySQL Cluster NDB 6.3 no longer in development. MySQL Cluster NDB 6.3 is no longer being actively developed; if you are using a MySQL Cluster NDB 6.3 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.3. You can download the latest MySQL Cluster NDB 6.3 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.28 (see Changes in MySQL 5.1.28 (2008-08-28)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
It is no longer a requirement for database autodiscovery that an SQL node already be connected to the cluster at the time that a database is created on another SQL node. It is no longer necessary to issue
CREATE SCHEMA) statements on an SQL node joining the cluster after a database is created for the new SQL node to see the database and any
NDBCLUSTERtables that it contains. (Bug #39612)
Starting the MySQL Server with the
--ndbclusteroption plus an invalid command-line option (for example, using mysqld
--ndbcluster --foobar) caused it to hang while shutting down the binary log thread. (Bug #39635)
Dropping and then re-creating a database on one SQL node caused other SQL nodes to hang. (Bug #39613)
Setting a low value of
MaxNoOfLocalScans(< 100) and performing a large number of (certain) scans could cause the Transaction Coordinator to run out of scan fragment records, and then crash. Now when this resource is exhausted, the cluster returns Error 291 (Out of scanfrag records in TC (increase MaxNoOfLocalScans)) instead. (Bug #39549)
When a transaction included a multi-row insert to an
NDBCLUSTERtable that caused a constraint violation, the transaction failed to roll back. (Bug #39538)
Creating a unique index on an
NDBCLUSTERtable caused a memory leak in the
NDBsubscription manager (
SUMA) which could lead to mysqld hanging, due to the fact that the resource shortage was not reported back to the
NDBkernel correctly. (Bug #39518)
References: See also Bug #39450.
Embedded libmysqld with
NDBdid not drop table events. (Bug #39450)
Unique identifiers in tables having no primary key were not cached. This fix has been observed to increase the efficiency of
INSERToperations on such tables by as much as 50%. (Bug #39267)
When restarting a data node, an excessively long shutdown message could cause the node process to crash. (Bug #38580)
After a forced shutdown and initial restart of the cluster, it was possible for SQL nodes to retain
.frmfiles corresponding to
NDBCLUSTERtables that had been dropped, and thus to be unaware that these tables no longer existed. In such cases, attempting to re-create the tables using
CREATE TABLE IF NOT EXISTScould fail with a spurious Table ... doesn't exist error. (Bug #37921)
A statement of the form
UPDATEwhere there was no row whose primary key column had the stated
valueappeared to succeed, with the server reporting that 1 row had been changed.
This issue was only known to affect MySQL Cluster NDB 6.3.11 and later NDB 6.3 versions. (Bug #37153)
Cluster Replication: In some cases, dropping a database on the master could cause table logging to fail on the slave, or, when using a debug build, could cause the slave mysqld to fail completely. (Bug #39404)