MySQL Cluster (MySQL 集群) 7.1.17 發布
MySQL Cluster 是 MySQL 適合于分布式計算環境的高實用、高冗余版本。它采用了NDB Cluster 存儲引擎，允許在1個 Cluster 中運行多個MySQL服務器。在MyQL 5.0及以上的二進制版本中、以及與最新的Linux版本兼容的RPM中提供了該存儲引擎。（注意，要想獲得MySQL Cluster 的功能，必須安裝 mysql-server 和 mysql-max RPM）。
MySQL Cluster 7.1.17 發布了，下載地址：
改進記錄：
MySQL Cluster NDB 7.1.17 is a new release of MySQL Cluster, incorporating new features in the NDBCLUSTER storage engine and fixing recently discovered bugs in MySQL Cluster NDB 7.1.16 and previous MySQL Cluster releases.
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.56 (see Section D.1.5, “Changes in MySQL 5.1.56 (01 March 2011)”).
Functionality Added or Changed
-
Introduced the
CrashOnCorruptedTupledata node configuration parameter. When enabled, this parameter causes data nodes to handle corrupted tuples in a fail-fast manner—in other words, whenever the data node detects a corrupted tuple, it forcibly shuts down ifCrashOnCorruptedTupleis enabled. For backward compatibility, this parameter is disabled by default. (Bug #12598636)
Bugs Fixed
-
When a failure of multiple data nodes during a local checkpoint (LCP) that took a long time to complete included the node designated as master, any new data nodes attempting to start before all ongoing LCPs were completed later crashed. This was due to the fact that node takeover by the new master cannot be completed until there are no pending local checkpoints. Long-running LCPs such as those which triggered this issue can occur when fragment sizes are sufficiently large (see Section 16.1.2, “MySQL Cluster Nodes, Node Groups, Replicas, and Partitions”, for more information). Now in such cases, data nodes (other than the new master) are kept from restarting until the takeover is complete. (Bug #13323589)