MySQL NDB Cluster 7.5 Release Notes
MySQL NDB Cluster 7.5.22 is a new release of MySQL NDB Cluster
7.5, based on MySQL Server 5.7 and including features in version
7.5 of the NDB
storage engine, as
well as fixing recently discovered bugs in previous NDB Cluster
releases.
Obtaining MySQL NDB Cluster 7.5. MySQL NDB Cluster 7.5 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/.
For an overview of changes made in MySQL NDB Cluster 7.5, see What is New in NDB Cluster 7.5.
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.34 (see Changes in MySQL 5.7.34 (2021-04-20, General Availability)).
A node was permitted during a restart to participate in a backup before it had completed recovery, instead of being made to wait until its recovery was finished. (Bug #32381165)
Running out of disk space while performing an
NDB
backup could lead to an unplanned
shutdown of the cluster.
(Bug #32367250)
The default number of partitions per node (shown in
ndb_desc output as
PartitionCount
) is calculated using the
lowest number of LDM threads employed by any single live node,
and was done only once, even after data nodes left or joined the
cluster, possibly with a new configuration changing the LDM
thread count and thus the default partition count. Now in such
cases, we make sure the default number of partitions per node is
recalculated whenever data nodes join or leave the cluster.
(Bug #32183985)
Event buffer congestion could lead to unplanned shutdown of SQL
nodes which were performing binary logging. We fix this by
updating the binary logging handler to use
Ndb::pollEvents2()
(rather than
the deprecated pollEvents()
method) to catch and handle such errors properly, instead.
(Bug #31926584)
Generation of internal statistics relating to
NDB
object counts was found to lead to an
increase in transaction latency at very high rates of
transactions per second, brought about by returning an excessive
number of freed NDB
objects.
(Bug #31790329)