MySQL Cluster NDB 7.2.13 is a new release of MySQL Cluster,
incorporating new features in the
NDB storage engine, and fixing
recently discovered bugs in previous MySQL Cluster NDB 7.2
Obtaining MySQL Cluster NDB 7.2. MySQL Cluster NDB 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/.
This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.31 (see Changes in MySQL 5.5.31 (2013-04-18)).
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 MySQL Cluster Management Client.
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; Cluster Replication:
The default value for the
binlog_format system variable
NDB storage engine is
enabled is now
NDB is not enabled, the default binary
logging format is
STATEMENT, as in the
standard MySQL Server.
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
References: See also Bug #11752792, Bug #44082.
WHERE condition that contained a boolean
test of the result of an
IN subselect was not
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
ndbd Error Messages).
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
fix also introduces a new
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
code (8013) has been added which causes a list a lagging
subscribers for each node to be printed to the cluster log (see
Purging the binary logs could sometimes cause mysqld to crash. (Bug #15854719)
An error message in
(Bug #14548052, Bug #66518)
The help text for ndb_select_count did not include any information about using table names. (Bug #11755737, Bug #47551)