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  /  Release Series Changelogs: MySQL NDB Cluster 7.6  /  Changes in MySQL NDB Cluster 7.6.30 (5.7.44-ndb-7.6.30) (2024-04-30, General Availability)

Changes in MySQL NDB Cluster 7.6.30 (5.7.44-ndb-7.6.30) (2024-04-30, General Availability)

Bugs Fixed

  • NDB Client Programs: ndb_redo_log_reader exited with Record type = 0 not implemented when reaching an unused page, all zero bytes, or a page which was only partially used (typically a page consisting of the page header only). (Bug #36313259)

  • Repeated incomplete incomplete attempts to perform a system restart in some cases left the cluster in a state from which it could not recover without restoring it from backup. (Bug #35801548)

  • The event buffer used by the NDB API maintains an internal pool of free memory to reduce the interactions with the runtime and operating system, while allowing memory that is no longer needed to be returned for other uses. This free memory is subtracted from the total allocated memory to determine the memory is use which is reported and used for enforcing buffer limits and other purposes; this was represented using a 32-bit value, so that if it exceeded 4 GB, the value wrapped, and the amount of free memory appeared to be reduced. This had potentially adverse effects on event buffer memory release to the runtime and OS, free memory reporting, and memory limit handling.

    This is fixed by using a 64-bit value to represent the amount of pooled free memory. (Bug #35483764)

    References: See also: Bug #35655162, Bug #35663761.

  • Removed unnecessary warnings generated by transient disconnections of data nodes during restore operations. (Bug #33144487)

  • In some cases, when trying to perform an online add index operation on an NDB table with no explicit primary key (see Limitations of NDB online operations), the resulting error message did not make the nature of the problem clear. (Bug #30766579)

    References: See also: Bug #36382071.