MySQL NDB Cluster 7.3.18 is a new release of NDB Cluster, based on
MySQL Server 5.6 and including features from version 7.3 of the
NDB
storage engine, as well as fixing
a number of recently discovered bugs in previous NDB Cluster
releases.
Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 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.3, see What is New in NDB Cluster 7.3.
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.6 through MySQL 5.6.37 (see Changes in MySQL 5.6.37 (2017-07-17, General Availability)).
Important Change; MySQL NDB ClusterJ: The ClusterJPA plugin for OpenJPA is no longer supported by NDB Cluster, and has been removed from the distribution. (Bug #23563810)
NDB Replication: Added a check to stop an
NDB
replication slave when configuration as a multithreaded slave is detected (for example, ifslave_parallel_workers
is set to a nonzero value). (Bug #21074209)MySQL NDB ClusterJ: Compilation for the tests for NDB JTie failed. It was due to how null references were handled, which has been corrected by this fix. (Bug #26080804)
Backup
.log
files contained log entries for one or more extra fragments, due to an issue with filtering out changes logged by other nodes in the same node group. This resulted in a larger.log
file and thus use of more resources than necessary; it could also cause problems when restoring, since backups from different nodes could interfere with one another while the log was being applied. (Bug #25891014)-
Error 240 is raised when there is a mismatch between foreign key trigger columns and the values supplied to them during trigger execution, but had no error message indicating the source of the problem. (Bug #23141739)
References: See also: Bug #23068914, Bug #85857.
ALTER TABLE .. MAX_ROWS=0
can now be performed only by using a copyingALTER TABLE
statement. ResettingMAX_ROWS
to 0 can no longer be performed usingALGORITHM=INPLACE
or theONLINE
keyword. (Bug #21960004)When compiling the NDB kernel with gcc version 6.0.0 or later, it is now built using
-flifetime-dse=1
. (Bug #85381, Bug #25690926)