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

MySQL NDB Cluster 7.6 Release Notes  /  Changes in MySQL NDB Cluster 7.6.31 (5.7.44-ndb-7.6.31) (2024-07-02, General Availability)

Changes in MySQL NDB Cluster 7.6.31 (5.7.44-ndb-7.6.31) (2024-07-02, General Availability)

MySQL NDB Cluster 7.6.31 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

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)).

Functionality Added or Changed

  • NDB Client Programs: When started, ndbd now produces a warning in the data node log like this one:

    2024-05-28 13:32:16 [ndbd] WARNING  -- Running ndbd with a single thread of
    signal execution.  For multi-threaded signal execution run the ndbmtd binary.

    (Bug #36326896)

Bugs Fixed

  • InnoDB: Some FTS operations on tables with FTS indexes led to inconsistent results. For example, if the server terminated while synchronizing the FTS cache or when synchronization occurred concurrently with another FTS operation.

    Our thanks to Yin Peng and the Tencent team for the contribution. (Bug #36347647)

  • NDB Client Programs: ndb_restore did not restore a foreign key whose columns differed in order from those of the parent key.

    Our thanks to Axel Svensson for the contribution. (Bug #114147, Bug #36345882)

  • Averages of certain numbers were not always computed correctly. (Bug #36741923)

    References: See also: Bug #36563773.

  • Running two concurrent OPTIMIZE TABLE statements on the same table with fulltext indexes and innodb_optimize_fulltext_only enabled sometimes caused the server to exit. (Bug #36741880)

    References: See also: Bug #36741880.

  • When distribution awareness was not in use, the cluster tended to choose the same data node as the transaction coordinator repeatedly. (Bug #35840020, Bug #36554026)