Documentation Home
MySQL NDB Cluster 7.4 Release Notes
Download these Release Notes
PDF (US Ltr) - 0.8Mb
PDF (A4) - 0.8Mb
HTML Download (TGZ) - 173.2Kb
HTML Download (Zip) - 253.1Kb


MySQL NDB Cluster 7.4 Release Notes  /  Changes in MySQL NDB Cluster 7.4.28 (5.6.48-ndb-7.4.28) (2020-04-28, General Availability)

Changes in MySQL NDB Cluster 7.4.28 (5.6.48-ndb-7.4.28) (2020-04-28, General Availability)

MySQL NDB Cluster 7.4.28 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases.

Obtaining MySQL NDB Cluster 7.4.  MySQL NDB Cluster 7.4 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/.

For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4.

This release also incorporates all bug fixes and changes made in previous NDB Cluster releases, as well as all bug fixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.48 (see Changes in MySQL 5.6.48 (2020-04-27, General Availability)) .

Functionality Added or Changed

  • NDB Client Programs: Removed a dependency from the ndb_waiter and ndb_show_tables utility programs on the NDBT library. This library, used in NDB development for testing, is not required for normal use. The visible effect for users from this change is that these programs no longer print NDBT_ProgramExit - status following completion of a run. Applications that depend upon this behavior should be updated to reflect this change when upgrading to this release.

  • Added the --ndb-log-fail-terminate option for mysqld. When used, this causes the SQL node to terminate if it is unable to log all row events. (Bug #21911930)

    References: See also: Bug #30383919.

Bugs Fixed

  • When a node ID allocation request failed with NotMaster temporary errors, the node ID allocation was always retried immediately, without regard to the cause of the error. This caused a very high rate of retries, whose effects could be observed as an excessive number of Alloc node id for node nnn failed log messages (on the order of 15,000 messages per second). (Bug #30293495)

  • For NDB tables having no explicit primary key, NdbReceiverBuffer could be allocated with too small a size. This was due to the fact that the attribute bitmap sent to NDB from the data nodes always includes the primary key. The extra space required for hidden primary keys is now taken into consideration in such cases. (Bug #30183466)