MySQL NDB Cluster 7.3 Release Notes

34.13 Changes in MySQL NDB Cluster 7.3.18 (5.6.37-ndb-7.3.18) (2017-07-18, General Availability)

Bugs Fixed

  • 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 copying ALTER TABLE statement. Resetting MAX_ROWS to 0 can no longer be performed using ALGORITHM=INPLACE or the ONLINE 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)