MySQL NDB Cluster 7.2 Release Notes
MySQL NDB Cluster 7.2.3 is a new development preview release of
NDB Cluster, incorporating new features in the
NDB
storage engine for testing and
user feedback.
Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from https://dev.mysql.com/downloads/cluster/.
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.5 through MySQL 5.5.17 (see Changes in MySQL 5.5.17 (2011-10-19, General Availability)).
Added the ThreadConfig
data node configuration parameter to enable control of multiple
threads and CPUs when using ndbmtd, by
assigning threads of one or more specified types to execute on
one or more CPUs. This can provide more precise and flexible
control over multiple threads than can be obtained using the
LockExecuteThreadToCPU
parameter.
(Bug #11795581)
Important Change; NDB Replication:
A unique key constraint violation caused
NDB
slaves to stop rather than to
continue when the
slave_exec_mode
was
IDEMPOTENT
. In such cases,
NDB
now behaves as other MySQL
storage engines do when in IDEMPOTENT
mode.
(Bug #11756310)
NDB Replication:
With many SQL nodes, all writing binary logs, connected to a
MySQL NDB Cluster, RENAME TABLE
could cause data node processes (ndbmtd) to
fail.
(Bug #13447705)
Added the MinFreePct
data node configuration parameter, which specifies a percentage
of data node resources to hold in reserve for restarts. The
resources monitored are
DataMemory
,
IndexMemory
, and any
per-table MAX_ROWS
settings (see
CREATE TABLE Statement). The default value of
MinFreePct
is 5, which
means that 5% from each these resources is now set aside for
restarts.
(Bug #13436216)
Issuing TRUNCATE TABLE
on
mysql.user
, mysql.host
,
mysql.db
,
mysql.tables_priv
,
mysql.proxies_priv
, or
mysql.procs_priv
, when these tables had been
converted to MySQL NDB Cluster distributed grant tables, caused
mysqld to crash.
(Bug #13346955)
Restarting an SQL node configured for distributed grants could sometimes result in a crash. (Bug #13340819)
Previously, forcing simultaneously the shutdown of multiple data
nodes using SHUTDOWN -F
in the
ndb_mgm management client could cause the
entire cluster to fail. Now in such cases, any such nodes are
forced to abort immediately.
(Bug #12928429)