Changes in MySQL NDB Cluster 7.6.35 (5.7.44-ndb-7.6.35) (2025-07-23, General Availability)

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

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

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

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.7 through MySQL 5.7.44 (see Changes in MySQL 5.7.44 (2023-10-25, General Availability)).

• Compilation Notes

• Functionality Added or Changed

• Bugs Fixed

Compilation Notes

• Solaris: Clang and GCC now can be used for compiling MySQL on Solaris. (Bug #30562248)

• MySQL Server now supports CMake 4, ensuring compatibility with future CMake versions where support for versions prior to 3.10 is expected to be discontinued. (Bug #38027636)

Functionality Added or Changed

• Important Change: Added the mysql client --commands option, which enables or disables most mysql client commands.

  This option is enabled by default. To disable it, start the client with --commands=OFF or --skip-commands.

  For a complete list of all commands affected by this option, and additional information, see mysql Client Options. (WL #16949)

  References: See also: Bug #36416568, Bug #38066040.

Bugs Fixed

• InnoDB: Fixed an issue relating to range queries on tables. (Bug #31360522)

  References: See also: Bug #38063122.

• Following an upgrade from NDB 8.0 to NDB 8.4, all data nodes in the cluster underwent an unexpected simultaneous restart. This occurred when the transaction coordinator had no scan state, leading to protocol timeout; the resulting misalignment in protocol states caused data nodes to shut down unexpectedly. This is fixed by extending existing handling of an unexpected SCAN_NEXTREQ signal to cover the case when the scan is already stateless. (Bug #37994985)

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

• WAIT_UNTIL_SQL_THREAD_AFTER_GTIDS() did not always execute correctly. (Bug #37829550)

  References: See also: Bug #38063175.

• Unquoted semicolon characters (;) within comments were not always flagged as errors, in spite of the fact that they are not allowed. (Bug #37117875)

  References: See also: Bug #38063286.