Changes in MySQL Cluster NDB 7.1.5 (5.1.47-ndb-7.1.5) (2010-06-25)

MySQL Cluster NDB 7.1.5 is a new release of MySQL Cluster,
incorporating new features in the
NDB storage engine and fixing
recently discovered bugs in MySQL Cluster NDB 7.1.4 and previous
MySQL Cluster releases.

This release also incorporates all bugfixes and 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.47 (see Changes in MySQL 5.1.47 (2010-05-06)).

Restrictions on some types of mismatches in column definitions
when restoring data using ndb_restore have
been relaxed. These include the following types of mismatches:

Different COLUMN_FORMAT settings
(FIXED, DYNAMIC,
DEFAULT)

Different STORAGE settings
(MEMORY, DISK)

Different default values

Different distribution key settings

Now, when one of these types of mismatches in column definitions
is encountered, ndb_restore no longer stops
with an error; instead, it accepts the data and inserts it into
the target table, while issuing a warning to the user.

It is now possible to install management node and data node
processes as Windows services. (See
Installing MySQL Cluster Processes as Windows Services, for
more information.) In addition, data node processes on Windows
are now maintained by angel processes, just as they are on other
platforms supported by MySQL Cluster.

Bugs Fixed

The disconnection of all API nodes (including SQL nodes) during
an ALTER TABLE caused a memory
leak.
(Bug #54685)

If a node shutdown (either in isolation or as part of a system
shutdown) occurred directly following a local checkpoint, it was
possible that this local checkpoint would not be used when
restoring the cluster.
(Bug #54611)

The setting for
BuildIndexThreads was
ignored by ndbmtd, which made it impossible
to use more than 4 cores for rebuilding indexes.
(Bug #54521)

When adding multiple new node groups to a MySQL Cluster, it was
necessary for each new node group to add only the nodes to be
assigned to the new node group, create that node group using
CREATE NODEGROUP, then repeat this process
for each new node group to be added to the cluster. The fix for
this issue makes it possible to add all of the new nodes at one
time, and then issue several CREATE NODEGROUP
commands in succession.
(Bug #54497)

When performing an online alter table where 2 or more SQL nodes
connected to the cluster were generating binary logs, an
incorrect message could be sent from the data nodes, causing
mysqld processes to crash. This problem was
often difficult to detect, because restarting SQL node or data
node processes could clear the error, and because the crash in
mysqld did not occur until several minutes
after the erroneous message was sent and received.
(Bug #54168)

A table having the maximum number of attributes permitted could
not be backed up using the ndb_mgm client.