Cases used in adding data node online to mysql cluster

Case 1:

Cluster Configuration:

Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 5 API1 (192.168.0.201)
Id = 6 API2 (192.168.0.202)

Then we down the two management nodes and add the new data node configuration as follow

New Cluster Configuration:

Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 5 API1 (192.168.0.201)
Id = 6 API2 (192.168.0.202)
Id = 7 NDBD3 (192.168.0.203)
Id = 8 API3 (192.168.0.203)

After saving this new configuration on the two management nodes and starting them again the
managemnt nodes read their configuration as :

Id = 1 MGM1 (192.168.0.200) UP
Id = 2 MGM2 (192.168.0.210) Up
Id = 3 NDBD1 (192.168.0.201) UP
Id = 4 NDBD2 (192.168.0.202) UP
Id = 7 NDBD3 (192.168.0.203) UP
Id = 8 API1 (192.168.0.201) Down
Id = 9 API2 (192.168.0.202) Down
Id = 10 API3 (192.168.0.203) UP

So API's Configuration is changed and the database is

lost .
Case 2:
Cluster Configuration:

Id = 1 MGM1
Id = 2 MGM2
Id = 3 NDBD1
Id = 4 NDBD2

The cluster is started without configuration set to API

nodes in order to avoid the problem in case1.
And The cluster configuration when running as follow:
Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 5 API1 (192.168.0.201)
Id = 6 API2 (192.168.0.202)

Then we down the two management nodes and add the following configuration :
Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 7 NDBD3 (192.168.0.203)
After saving this new configuration on the two management nodes and starting them again the
managemnt nodes read their configuration as :

Id = 1 MGM1 (192.168.0.200) UP
Id = 2 MGM2 (192.168.0.210) UP
Id = 3 NDBD1 (192.168.0.201) UP
Id = 4 NDBD2 (192.168.0.202) UP
Id = 7 NDBD3 (192.168.0.203) UP
Id = 8 API1 (192.168.0.201) Down
Id = 9 API2 (192.168.0.202) Down
Id = 10 API3 (192.168.0.203) UP

So API's Configuration is changed and the database is

lost .
We Rolled back all this configuration and start this case again but setting new data node ndbd id = 5
but when we get the two management up the following configuration showed up:
Id = 1 MGM1 (192.168.0.200) UP
Id = 2 MGM2 (192.168.0.210) UP
Id = 3 NDBD1 (192.168.0.201) UP
Id = 4 NDBD2 (192.168.0.202) UP
Id = 5 NDBD3 (192.168.0.203) UP
Id = 6 API1 (192.168.0.201) Down
Id = 7 API2 (192.168.0.202) Down
Id = 8 API3 (192.168.0.203) UP

So API's Configuration is changed again and the

database is lost .
Case 3:
Cluster Configuration :

Before Starting up Cluster we will set API's Id's manually with wide range from NDBD node's id and
the following is the configuration set on yhe two management node's :
Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 20 API1 (192.168.0.201)
Id = 21 API2 (192.168.0.202)

Then we get the two management nodes up and they read configuration as :

Id = 1 MGM1 (192.168.0.200) UP
Id = 2 MGM2 (192.168.0.210) UP
Id = 3 NDBD1 (192.168.0.201) UP
Id = 4 NDBD2 (192.168.0.202) UP
Id = 20 API1 (192.168.0.201) UP
Id = 21 API2 (192.168.0.202) UP
Id = 22 API Accepting from any node
Id = 23 API Accepting from any node

Then we down the two management nodes and add the following configuration :
Id = 1 MGM1 (192.168.0.200)
Id = 2 MGM2 (192.168.0.210)
Id = 3 NDBD1 (192.168.0.201)
Id = 4 NDBD2 (192.168.0.202)
Id = 5 NDBD3 (192.168.0.203)
id = 20 API1 (192.168.0.201)
Id = 21 API2 (192.168.0.202)
Id = 22 API3 (192.168.0.203)

After saving this new configuration on the two management nodes and starting them again the
managemnt nodes read their configuration as :

Id = 1 MGM1 (192.168.0.200) UP
Id = 2 MGM2 (192.168.0.210) UP
Id = 3 NDBD1 (192.168.0.201) UP
Id = 4 NDBD2 (192.168.0.202) UP
Id = 5 NDBD3 (192.168.0.203) DOWN
Id = 20 API1 (192.168.0.201) UP
Id = 21 API2 (192.168.0.202) UP
Id = 22 API3 (192.168.0.203) DOWN

So API's Configuration doesn't change and the database

is still running .

Case 4: Changing Data Memory Parameter :

The two management nodes are down and then we changed the DataMemoty Parameter in config.ini
file in both management nodes and then get the two management nodes up ,But the Data nodes doesn't
sense this change in the configuration.