MySQL Cluster NDB 7.1.12 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.1
Obtaining MySQL Cluster NDB 7.1. The latest MySQL Cluster NDB 7.1 binaries for supported platforms can be obtained from http://dev.mysql.com/downloads/cluster/. Source code for the latest MySQL Cluster NDB 7.1 release can be obtained from the same location. You can also access the MySQL Cluster NDB 7.1 development source tree at https://code.launchpad.net/~mysql/mysql-server/mysql-cluster-7.1.
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.1 through MySQL 5.1.51 (see Changes in MySQL 5.1.51 (2010-09-10)).
Improved scaling of ordered index scans performance by removing a hard-coded limit (
MAX_PARALLEL_INDEX_SCANS_PER_FRAG) and making the number of
TUXscans per fragment configurable by adding the
MaxParallelScansPerFragmentdata node configuration parameter. (Bug #11769048)
Important Change: Formerly, the
--ndb-cluster-connection-poolserver option set a status variable as well as a system variable. The status variable has been removed as redundant. (Bug #60119)
A scan with a pushed condition (filter) using the
CommittedReadlock mode could hang for a short interval when it was aborted when just as it had decided to send a batch. (Bug #11932525)
When aborting a multi-read range scan exactly as it was changing ranges in the local query handler, LQH could fail to detect it, leaving the scan hanging. (Bug #11929643)
Schema distribution did not take place for tables converted from another storage engine to
ALTER TABLE; this meant that such tables were not always visible to all SQL nodes attached to the cluster. (Bug #11894966)
A GCI value inserted by ndb_restore
ndb_apply_statustable was actually 1 less than the correct value. (Bug #11885852)
Disk Data: Limits imposed by the size of
SharedGlobalMemorywere not always enforced consistently with regard to Disk Data undo buffers and log files. This could sometimes cause a
CREATE LOGFILE GROUPor
ALTER LOGFILE GROUPstatement to fail for no apparent reason, or cause the log file group specified by
InitialLogFileGroupnot to be created when starting the cluster. (Bug #57317)
Cluster Replication: Filtering the binary log using
--binlog-ignore-db=mysqlcaused epochs not to be logged as expected in the
ndb_apply_statustable. (Bug #11765707, Bug #58698)
ClusterJ: Binary columns can now be used as key columns.
Error reporting when trying to use unsupported column types has been improved.
DynamicObjectpersistent classes are now handled as expected. (Bug #11766757, Bug #59942)
The optimizer sometimes requested ordered access from a storage engine when ordered access was not required. (Bug #57601, Bug #11764737)