This is a new source 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 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.24 (see Changes in MySQL 5.1.24 (2008-04-08)).
Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
A race condition caused by a failure in epoll handling could cause data nodes to fail. (Bug #36537)
Under certain rare circumstances, the failure of the new master node while attempting a node takeover would cause takeover errors to repeat without being resolved. (Bug #36199, Bug #36246, Bug #36247, Bug #36276)
When more than one SQL node connected to the cluster at the same
time, creation of the
failed on one of them with an explicit Table
exists error, which was not necessary.
mysqld failed to start after running mysql_upgrade. (Bug #35708)
SET GLOBAL ndb_extra_logging caused
mysqld to crash.
NDB error 1427 (Api node
died, when SUB_START_REQ reached node) was
incorrectly classified as a schema error rather than a temporary
If an API node disconnected and then reconnected during Start
Phase 8, then the connection could be
“blocked”—that is, the
QMGR kernel block failed to detect that the
API node was in fact connected to the cluster, causing issues
NDB Subscription Manager
Notification of a cascading master node failures could sometimes
not be transmitted correctly (that is, transmission of the
NF_COMPLETEREP signal could fail), leading to
transactions hanging and timing out
NDB error 4012), scans hanging,
and failure of the management server process.
SELECT ... FROM
mysql.ndb_apply_status before the
mysqld process had connected to the cluster
failed, and caused this table never to be created.
Accessing the debug version of
dlopen() resulted in a segmentation
Attempting to pass a nonexistent column name to the
NdbOperation caused NDB API
applications to crash. Now the column name is checked, and an
error is returned in the event that the column is not found.
Relocation errors were encountered when trying to compile NDB
API applications on a number of platforms, including 64-bit
Linux. As a result,
have been changed from normal libraries to “noinst”
libtool helper libraries. They are no longer
installed as separate libraries; instead, all necessary symbols
from these are added directly to
libndbclient. This means that NDB API
programs now need to be linked using only
(Bug #29791, Bug #11746931)