2 Changes in MySQL NDB Cluster 8.0.45 (2026-01-22, General Availability)

MySQL NDB Cluster 8.0.45 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.45 (see Changes in MySQL 8.0.45 (2026-01-20, General Availability)).

Note

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

Functionality Added or Changed

Reporting of File Close errors has been improved. (Bug #38726643)
The option --skip-fk-checks was added to ndb_restore. This option modifies the behavior of --rebuild-indexes so that, when foreign keys are re-enabled, the existing data in the table is not checked for consistency. (Bug #38593666)
The logs generated for backup and restore operations are improved in this release. (Bug #38592288)

Bugs Fixed

The NDB purge process responsible for removing rows from mysql.ndb_binlog_index when a binary log file is purged, assumed that autocommit is enabled, and each DML operation commits immediately. However, if autocommit is disabled globally, the purge process inherited this value and purge operations were not committed.
As of this release, autocommit is enabled for the purge session, even when the global setting is disabled. (Bug #38488185)
NDB data nodes failed to start if either of the NDBCNTR or DBDIH system files were empty. (Bug #38424959)
A data node failure occurred due to a reference validity check which failed. (Bug #38422448)
BackupRecords in a participant node were not released from the pool when a backup was aborted, causing subsequent backup operations to fail. (Bug #38151265)
The ndb_restore log message for total log bytes restored was incorrect (Bug #37697971)
ndb_log_bin could be set dynamically, but had no effect. This variable is not dynamic and is only checked when the binlog thread starts. (Bug #32860560)