MySQL NDB Cluster 7.2 Release Notes
NDB Cluster APIs:
Added DUMP code 2514, which provides
information about counts of transaction objects per API node.
For more information, see DUMP 2514.
See also Commands in the NDB Cluster Management Client.
(Bug #15878085)
When ndb_restore fails to find a table, it now includes in the error output an NDB API error code giving the reason for the failure. (Bug #16329067)
Incompatible Change; NDB Replication:
The default value for the
binlog_format system variable
when the NDB storage engine is
enabled is now MIXED. If
NDB is not enabled, the default binary
logging format is STATEMENT, as in the
standard MySQL Server.
(Bug #16417224)
NDB Disk Data:
NDB error 899 RowId already
allocated was raised due to a RowId
“leak” which occurred under either of the following
sets of circumstances:
Insertion of a row into an in-memory table was rejected
after an ordered index update failed due to insufficient
DataMemory.
Insertion of a row into a Disk Data table was rejected due to lack of sufficient table space.
(Bug #13927679)
References: See also: Bug #22494024, Bug #13990924.
The NDB Error-Reporting Utility
(ndb_error_reporter) failed to include the
cluster nodes' log files in the archive it produced when the
FILE option was set for the parameter
LogDestination.
(Bug #16765651)
References: See also: Bug #11752792, Bug #44082.
A WHERE condition that contained a boolean
test of the result of an IN subselect was not
evaluated correctly.
(Bug #16678033)
In some cases a data node could stop with an exit code but no
error message other than (null) was logged.
(This could occur when using ndbd or
ndbmtd for the data node process.) Now in
such cases the appropriate error message is used instead (see
Data Node Error Messages).
(Bug #16614114)
mysql_upgrade failed when run on an SQL node where distributed privileges were in use. (Bug #16226274)
Improved handling of lagging row change event subscribers by
setting size of the GCP pool to the value of
MaxBufferedEpochs. This
fix also introduces a new
MaxBufferedEpochBytes
data node configuration parameter, which makes it possible to
set a total number of bytes per node to be reserved for
buffering epochs. In addition, a new DUMP
code (8013) has been added which causes a list a lagging
subscribers for each node to be printed to the cluster log (see
DUMP 8013).
(Bug #16203623)
Purging the binary logs could sometimes cause mysqld to crash. (Bug #15854719)
An error message in src/mgmsrv/MgmtSrvr.cpp
was corrected.
(Bug #14548052, Bug #66518)
The help text for ndb_select_count did not include any information about using table names. (Bug #11755737, Bug #47551)