Scenario: Grow from two data nodes to four using ONLINE ADD NODE and REORGANIZE PARTITION of a 2GB table, and UPDATE traffic

Setup for each data node:
* Dual cpu - quad core running at 2.33GHz.
* 8GB of RAM
* DataMemory=4096MB
* MaxNoOfExecutionThreads=8
* Configuration generated by Configurator
* Bound execution threads to cores (LockExec/Maint....Thread..)
* Completely distributed setup.

Created the following table and filled it with 2M rows which gives a table (different of last time to simplify further tests) of 2GB in size:

CREATE TABLE `t1` (
`a` bigint(20) unsigned NOT NULL AUTO_INCREMENT,
`b` int(10) unsigned DEFAULT NULL,
`c` timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
`d` varbinary(768) DEFAULT NULL,
`e` varbinary(256) DEFAULT NULL,
…

I want to measure the time it takes to do various ONLINE ADD NODE operations in MySQL Cluster 7.0 and especially how long time it takes to repartition the data onto the newly added nodes. So here comes the first post on the subject.

First off: Go from two data nodes to four using ONLINE ADD NODE and REORGANIZE PARTITION of 2GB tables, and no traffic system.

Setup for each data node:

• Dual cpu - quad core running at 2.33GHz.
• 8GB of RAM
• DataMemory=4096MB
• MaxNoOfExecutionThreads=8
• Configuration generated by Configurator
• Bound execution threads to cores (LockExec/Maint....Thread..)
  
• Completely distributed setup.
  
…

MySQL Cluster 7.0.4 (beta, a and formerly known as 6.4) was released yesterday in source format. The new versions fixes a number of bugs in e.g the areas of online add node and parition pruning for some index scans.

Morveover Configurator has been updated (and all the scripts have got improved error handling and usability) to support add nodes with a procedure according to the docs.

To add a new node group using the Configurator you do like this:

1. Make sure you have a MySQL Cluster 7.0 running.
   
2. cd mysqlcluster-70/cluster/scripts
3. Add the two new data nodes to the config.ini
   
   • vi …