This is the first development release for MySQL Cluster NDB 6.3,
based on version 6.3 of the
NDBCLUSTER storage engine.
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 feature 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.19 (see Changes in MySQL 5.1.19 (2007-05-25)).
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
Reporting functionality has been significantly enhanced in this release:
A new configuration parameter
now makes it possible to cause the management client to
provide status reports at regular intervals as well as for
such reports to be written to the cluster log (depending on
cluster event logging levels).
REPORT command has been added in
the cluster management client.
BackupStatus enables you to obtain a backup status
report at any time during a backup.
MemoryUsage reports the current data memory and
index memory used by each data node. For more about the
REPORT command, see
Commands in the MySQL Cluster Management Client.
ndb_restore now provides running reports of its progress when restoring a backup. In addition, a complete report status report on the backup is written to the cluster log.
Cluster Replication: This release implements conflict resolution, which makes it possible to determine on a per-table basis whether or not an update to a given row on the master should be applied on the slave. For more information, see MySQL Cluster Replication Conflict Resolution.