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:

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.

For more information, see ndb_restore — Restore a MySQL Cluster Backup. (Bug #54423)

References: See also Bug #53810, Bug #54178, Bug #54242, Bug #54279.

Introduced the HeartbeatOrder data node configuration parameter, which can be used to set the order in which heartbeats are transmitted between data nodes. This parameter can be useful in situations where multiple data nodes are running on the same host and a temporary disruption in connectivity between hosts would otherwise cause the loss of a node group, leading to failure of the cluster. (Bug #52182)

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.

The two MySQL Server options, --ndb-wait-connected and --ndb-wait-setup, did not set the corresponding system variables. (Bug #48402)

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)

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)

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

During initial node restarts, initialization of the REDO log was always performed 1 node at a time, during start phase 4. Now this is done during start phase 2, so that the initialization can be performed in parallel, thus decreasing the time required for initial restarts involving multiple nodes. (Bug #50062)

The presence of duplicate [tcp] sections in the config.ini file caused the management server to crash. Now in such cases, ndb_mgmd fails gracefully with an appropriate error message. (Bug #49400)

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

(Bug #54155)

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)

Cluster Replication: An error in an NDB internal byte mask value could lead to corruption of replicated BIT column values. (Bug #54005)

References: See also Bug #53622.

Cluster API: When using the NDB API, it was possible to rename a table with the same name as that of an existing table.

(Bug #54651)

Cluster API: An excessive number of client connections, such that more than 1024 file descriptors, sockets, or both were open, caused NDB API applications to crash. (Bug #34303)