MySQL NDB Cluster 7.2 Release Notes
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)
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)