This is a new Beta development release, fixing recently discovered bugs in previous MySQL Cluster NDB 6.3 releases.
Obtaining MySQL Cluster NDB 6.3. This is a source-only release, which you must compile and install using the instructions found in Section 2.3, “MySQL Installation Using a Source Distribution”, and in Section 17.2.1, “MySQL Cluster Multi-Computer Installation”. 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 Section C.1.30, “Changes in MySQL 5.1.22 (24 September 2007 Release Candidate)”).
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:
option for mysqld now allows a wider range of
values and corresponding behaviors for SQL nodes when selecting
a transaction coordinator.
You should be aware that the default value and behavior as well
as the value type used for this option have changed, and that
you may need to update the setting used for this option in your
my.cnf file prior to upgrading
Section 5.1.4, “Server System Variables”, for more information.
Cluster Replication: Replication: A replication heartbeat mechanism has been added to facilitate monitoring. This provides an alternative to checking log files, making it possible to detect in real time when a slave has failed.
Configuration of heartbeats is done via a new
clause for the
CHANGE MASTER TO statement (see
Section 188.8.131.52, “
CHANGE MASTER TO Syntax”); monitoring can be done by
checking the values of the status variables
Section 5.1.7, “Server Status Variables”).
The addition of replication heartbeats addresses a number of issues:
On MySQL replication slaves having multiple network interfaces,
it is now possible to set which interface to use for connecting
to the master. This can be done by using either the
mysqld startup option
--master-bind or the
clause in a
CHANGE MASTER TO
A new configuration parameter
TimeBetweenEpochsTimeout allows a timeout to
be set for time between epochs. For more information, see
Section 184.108.40.206, “Defining MySQL Cluster Data Nodes”.
Support for a new conflict resolution function
NDB$OLD() has been added for handling
simultaneous updates in multi-master and circular replication
setups. A new status variable
Ndb_conflict_fn_old tracks the
number of times that updates are prevented from being applied
due to this type of conflict resolution. See
Section 17.6.11, “MySQL Cluster Replication Conflict Resolution”,
for more information.
Additional checks were implemented to catch unsupported online
ALTER TABLE operations. Currently
it is not possible to reorder columns or to change the storage
engine used for a table via online
Some redundant checks made during online creation of indexes were removed.
--bind-address option has been
added to a number of MySQL client programs:
and mysqlshow. This is for use on a computer
having multiple network interfaces, and allows you to choose
which interface is used to connect to the MySQL server.
It was possible in some cases for a node group to be “lost” due to missed local checkpoints following a system restart. (Bug#31525)
NDB tables having names containing
nonalphanumeric characters (such as
$”) were not discovered
A node failure during a local checkpoint could lead to a subsequent failure of the cluster during a system restart. (Bug#31257)
A cluster restart could sometimes fail due to an issue with table IDs. (Bug#30975)
Transaction timeouts were not handled well in some circumstances, leading to excessive number of transactions being aborted unnecessarily. (Bug#30379)
In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)
--help did not
display any information about the
An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)
The cluster log was formatted inconsistently and contained extraneous newline characters. (Bug#25064)
A transaction was not aborted following the failure of statement. (Bug#31320)
Errors could sometimes occur during an online
COLUMN under load.