- 17.1.4 MySQL Cluster Development History
- 17.1.4.1 Development History of MySQL Cluster in MySQL 5.1
- 17.1.4.2 MySQL Cluster Development in MySQL Cluster NDB 6.1
- 17.1.4.3 MySQL CLuster Development in MySQL Cluster NDB 6.2
- 17.1.4.4 MySQL Cluster Development in MySQL Cluster NDB 6.3
- 17.1.4.5 MySQL Cluster Development in MySQL Cluster NDB 7.0
- 17.1.4.6 MySQL Cluster Development in MySQL Cluster NDB 7.1
The following list provides an overview of significant feature additions and changes made in MySQL Cluster NDB 6.1. All of the changes in this list are also available in MySQL Cluster NDB 6.2 and 6.3 releases. For detailed information about all changes made in MySQL Cluster NDB 6.1, see Section 17.7.5, “Changes in MySQL Cluster NDB 6.1”.
Increased number of cluster nodes. The maximum number of all nodes in a MySQL Cluster has been increased to 255. For more information, see Section 17.1.5.10, “Limitations Relating to Multiple MySQL Cluster Nodes”.
Disabling arbitration. It is now possible to disable arbitration by setting
ArbitrationRank=0on all cluster management and SQL nodes. For more information, see Defining the Management Server:ArbitrationRankand Defining SQL and Other API Nodes:ArbitrationRank.Additional
DUMPcommands. New management clientDUMPcommands provide help with tracking transactions, scan operations, and locks. See Section 17.5.2, “Commands in the MySQL Cluster Management Client”, andDUMPCommands, for more information.Faster Disk Data backups. Improvements in backups of Disk Data tables can yield a 10 to 15% increase in backup speed of Disk Data tables.
Batched slave updates. Batching of updates on cluster replication slaves, enabled using the
--slave-allow-batchingoption for mysqld, increases replication efficiency. For more information, see Section 17.6.6, “Starting MySQL Cluster Replication (Single Replication Channel)”.
User Comments
Add your own comment.