Changes in MySQL NDB Cluster 8.4.6 (2025-07-23, LTS Release)

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

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

For an overview of major changes made in NDB Cluster 8.4, see What is New in MySQL NDB Cluster 8.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 8.4 through MySQL 8.4.6 (see Changes in MySQL 8.4.6 (2025-07-22, LTS Release)).

Note

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

• Functionality Added or Changed

• Bugs Fixed

Functionality Added or Changed

• Timestamps in NDB node logs can now be printed with microsecond resolution. Data nodes can enable this feature using the data node --ndb-log-timestamps=UTC option; management nodes can also do so using the ndb_mgmd option --ndb-log-timestamps=UTC. For backwards compatible behavior, you can set this option explicitly to LEGACY, which uses the system time zone and resolution in seconds, as in previous releases. In NDB 8.4, this is the default.

  For SQL nodes, use the --log-timestamps option; be aware that this mysqld option does not support LEGACY as a value.

  See NDB Cluster Log Messages, for more information. (Bug #37924338)

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)

• Warning 1296 The temporary named table ... already exists showed the table and schema names in the wrong order.

  Our thanks to Axel Svensson for the contribution. (Bug #117918, Bug #37807409)