Documentation Home
MySQL NDB Cluster 8.0 Release Notes
Related Documentation Download these Release Notes
PDF (US Ltr) - 2.0Mb
PDF (A4) - 2.0Mb


MySQL NDB Cluster 8.0 Release Notes  /  Changes in MySQL NDB Cluster 8.0.43 (2025-07-23, General Availability)

Changes in MySQL NDB Cluster 8.0.43 (2025-07-23, General Availability)

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

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

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

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 8.0 through MySQL 8.0.43 (see Changes in MySQL 8.0.43 (2025-07-22, General Availability)).

Note

These release notes were created with the assistance of MySQL HeatWave GenAI.

Bugs Fixed

  • NDB Client Programs: ndb_restore, when applying the log, allowed an infinite number of retries due to temporary errors, rather than limiting these to 11 as expected. (Bug #37883579)

    References: This issue is a regression of: Bug #31546136.

  • NDB Client Programs: When restoring from backup with DefaultOperationRedoProblemAction=ABORT, an error in data node handling of a redo log part overload condition resulted in an incorrect error code (626 in this case) being sent back to ndb_restore, which caused ndb_restore to exit prematurely since it did not expect such an error. (Bug #37687485)

    References: This issue is a regression of: Bug #13219, Bug #13930, Bug #13980.

  • Improved password handling for file system encryption.

    Our thanks to Axel Svensson for the contribution. (Bug #37909595)

  • CREATE TABLESPACE, when the specified logfile group did not exist, was rejected with error 723 No such table existed, which did not correctly identify the source of the problem with the SQL statement. Now in such cases, the server issues Error 789 Logfile group not found. (Bug #37802388)