This is a new Beta development release, fixing recently discovered bugs in previous MySQL Cluster releases.
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. This is a source-only release, which you must compile and install using the instructions found in Installing MySQL from Source, and in MySQL Cluster Installation and Upgrades. You can download the GPL source tarball from the MySQL FTP site at ftp://ftp.mysql.com/pub/mysql/download/cluster_telco/.
This Beta release incorporates all bugfixes and changes made in the previous MySQL Cluster NDB 6.3 release, 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.
Important Note: MySQL Cluster NDB 6.2 and 6.3 source archives are now available in separate commercial and GPL versions. Due to licensing concerns, previous MySQL Cluster NDB 6.2 and 6.3 source archives were removed from the FTP site.
The output of the ndb_mgm client
STATUScommands now indicates when the cluster is in single user mode. (Bug #27999)
Unnecessary reads when performing a primary key or unique key update have been reduced, and in some cases, eliminated. (It is almost never necessary to read a record prior to an update, the lone exception to this being when a primary key is updated, since this requires a delete followed by an insert, which must be prepared by reading the record.) Depending on the number of primary key and unique key lookups that are performed per transaction, this can yield a considerable improvement in performance.
In a cluster running in diskless mode and with arbitration disabled, the failure of a data node during an insert operation caused other data node to fail. (Bug #31980)
An insert or update with combined range and equality constraints failed when run against an
NDBtable with the error Got unknown error from NDB. An example of such a statement would be
UPDATE t1 SET b = 5 WHERE a IN (7,8) OR a >= 10;. (Bug #31874)
An error with an
sql/ha_ndbcluster.cccould potentially lead to an infinite loop in case of failure when working with
NDBtables. (Bug #31810)
NDBstorage engine code was not safe for strict-alias optimization in gcc 4.2.1. (Bug #31761)
ndb_restore displayed incorrect backup file version information. This meant (for example) that, when attempting to restore a backup made from a MySQL 5.1.22 cluster to a MySQL Cluster NDB 6.3.3 cluster, the restore process failed with the error Restore program older than backup version. Not supported. Use new restore program. (Bug #31723)
Following an upgrade, ndb_mgmd failed with an ArbitrationError. (Bug #31690)
NDBmanagement client command
provided no output when
node_idwas the node ID of a management or API node. Now, when this occurs, the management client responds with
Node. (Bug #29485)
node_id: is not a data node
DELETEoperations after a data node had been shut down could lead to inconsistent data following a restart of the node. (Bug #26450)
UPDATE IGNOREcould sometimes fail on
NDBtables due to the use of unitialized data when checking for duplicate keys to be ignored. (Bug #25817)
Replication; Cluster Replication: A node failure during replication could lead to buckets out of order; now active subscribers are checked for, rather than empty buckets. (Bug #31701)
Cluster Replication: Updates performed unnecessary writes to the primary keys of the rows being updated. (Bug #31841)
Cluster Replication: Slave batching did not work correctly with
UPDATEstatements. (Bug #31787)
Cluster Replication: When the master mysqld crashed or was restarted, no
LOST_EVENTSentry was made in the binlog. (Bug #31484)
References: See also: Bug #21494.