Documentation Home
MySQL NDB Cluster 7.4 Release Notes
Download these Release Notes
PDF (US Ltr) - 0.9Mb
PDF (A4) - 0.9Mb


MySQL NDB Cluster 7.4 Release Notes  /  Changes in MySQL NDB Cluster 7.4.35 (5.6.51-ndb-7.4.35) (2022-01-19, General Availability)

Changes in MySQL NDB Cluster 7.4.35 (5.6.51-ndb-7.4.35) (2022-01-19, General Availability)

MySQL NDB Cluster 7.4.35 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.

Bugs Fixed

  • NDB Cluster APIs: It is no longer possible to use the DIVERIFYREQ signal asynchronously. (Bug #33161562)

  • Added missing values checks in ndbd and ndbmtd. (Bug #33661024)

  • In certain cases, an event's category was not properly detected. (Bug #33304814)

  • DBDICT did not always perform table name checks correctly. (Bug #33161548)

  • SET_LOGLEVELORD signals were not always handled correctly. (Bug #33161246)

  • DUMP 11001 did not always handle all of its arguments correctly. (Bug #33157513)

  • File names were not always verified correctly. (Bug #33157475)

  • Added a number of missing ID and other values checks in ndbd and ndbmtd. (Bug #32983700, Bug #32893708, Bug #32957478, Bug #32983256, Bug #32983339, Bug #32983489, Bug #32983517, Bug #33157527, Bug #33157531, Bug #33161271, Bug #33161298, Bug #33161314, Bug #33161331, Bug #33161372, Bug #33161462, Bug #33161511, Bug #33161519, Bug #33161537, Bug #33161570, Bug #33162059, Bug #33162065, Bug #33162074, Bug #33162082, Bug #33162092, Bug #33162098, Bug #33304819)

  • The management server did not always handle events of the wrong size correctly. (Bug #32957547)