This is the first MySQL Cluster NDB 6.1 release, incorporating
new features and bugfixes made for the
NDBCLUSTER storage engine made
since branching from MySQL 5.1.14 standard (see
Section C.1.38, “Changes in MySQL 5.1.14 (05 December 2006)”).
MySQL Cluster NDB 6.1 no longer in development. MySQL Cluster NDB 6.1 (formerly known as “MySQL Cluster Carrier Grade Edition 6.1.x”) is no longer being developed or maintained; if you are using a MySQL Cluster NDB 6.1 release, you should consider upgrading to MySQL Cluster NDB 6.2 or 6.3.
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:
A new configuration parameter
MemReportFrequency allows for additional
control of data node memory usage. Previously, only warnings at
predetermined percentages of memory allocation were given;
setting this parameter allows for that behavior to be
overridden. For more information, see
Section 220.127.116.11, “Defining MySQL Cluster Data Nodes”.
When a data node was shut down using the management client
STOP command, a connection event
NDB_LE_Connected) was logged instead of a
disconnection event (
Disk Data: Performing a node restart with a newly dropped Disk Data table could lead to failure of the node during the restart. (Bug#24917)
Disk Data: When restoring from backup a cluster containing any Disk Data tables with hidden primary keys, a node failure resulted which could lead to a crash of the cluster. (Bug#24166)
Extents that should have been available for re-use following a
DROP TABLE operation were not
actually made available again until after the cluster had
performed a local checkpoint.
using execution type
Commit and abort option
AO_IgnoreError could lead to a crash of the
transaction coordinator (
Cluster API: A unique index lookup on a nonexistent tuple could lead to a data node timeout (error 4012). (Bug#25059)
When using the
method, a very long timeout (greater than 5 minutes) could
result if the last data node being polled was disconnected from
Cluster API: Due to an error in the computation of table fragment arrays, some transactions were not executed from the correct starting point. (Bug#24914)
Under certain rare circumstances, local checkpoints were not performed properly, leading to an inability to restart one or more data nodes. (Bug#24664)