MySQL NDB Cluster 7.5 Release Notes
MySQL NDB Cluster 7.5.8 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.20 (see Changes in MySQL 5.7.20 (2017-10-16, General Availability)).
MySQL NDB ClusterJ: ClusterJ now supports CPU binding for receive threads through the setRecvThreadCPUids() and getRecvThreadCPUids() methods. Also, the receive thread activation threshold can be set and get with the setRecvThreadActivationThreshold() and getRecvThreadActivationThreshold() methods. (WL #10815)
Replication:
With GTIDs generated for incident log events, MySQL error code
1590 (ER_SLAVE_INCIDENT) could not be skipped using the
--slave-skip-errors=1590 startup option on a
replication slave.
(Bug #26266758)
Errors in parsing NDB_TABLE modifiers could
cause memory leaks.
(Bug #26724559)
Added DUMP code 7027 to facilitate testing of
issues relating to local checkpoints. For more information, see
DUMP 7027.
(Bug #26661468)
A previous fix intended to improve logging of node failure handling in the transaction coordinator included logging of transactions that could occur in normal operation, which made the resulting logs needlessly verbose. Such normal transactions are no longer written to the log in such cases. (Bug #26568782)
References: This issue is a regression of: Bug #26364729.
Due to a configuration file error, CPU locking capability was not available on builds for Linux platforms. (Bug #26378589)
Some DUMP codes used for the
LGMAN kernel block were incorrectly assigned
numbers in the range used for codes belonging to
DBTUX. These have now been assigned symbolic
constants and numbers in the proper range (10001, 10002, and
10003).
(Bug #26365433)
Node failure handling in the DBTC kernel
block consists of a number of tasks which execute concurrently,
and all of which must complete before TC node failure handling
is complete. This fix extends logging coverage to record when
each task completes, and which tasks remain, includes the
following improvements:
Handling interactions between GCP and node failure handling interactions, in which TC takeover causes GCP participant stall at the master TC to allow it to extend the current GCI with any transactions that were taken over; the stall can begin and end in different GCP protocol states. Logging coverage is extended to cover all scenarios. Debug logging is now more consistent and understandable to users.
Logging done by the QMGR block as it
monitors duration of node failure handling duration is done
more frequently. A warning log is now generated every 30
seconds (instead of 1 minute), and this now includes
DBDIH block debug information (formerly
this was written separately, and less often).
To reduce space used, DBTC instance
is shortened to
number:DBTC .
number:
A new error code is added to assist testing.
(Bug #26364729)
NDB Cluster did not compile successfully when the build used
WITH_UNIT_TESTS=OFF.
(Bug #86881, Bug #26375985)
A potential hundredfold signal fan-out when sending a
START_FRAG_REQ signal could lead to a node
failure due to a job buffer full error in
start phase 5 while trying to perform a local checkpoint during
a restart.
(Bug #86675, Bug #26263397)
References: See also: Bug #26288247, Bug #26279522.
Compilation of NDB Cluster failed when using
-DWITHOUT_SERVER=1 to build only the client
libraries.
(Bug #85524, Bug #25741111)