content_image/863112.jpg
) ENGINE NDBCLUSTER; 

The memory usage and related information shown later in this section was generated after inserting approximately 50000 rows into this table. 

<img src='content_image/863112.jpg'>

## Note 

In this example, we show the single-threaded ndbd  being used for the data node processes. You can also apply this example, if you are using the multithreaded ndbmtd  by substituting ndbmtd  for ndbd  wherever it appears in the steps that follow. 

Step 1: Update configuration file.  Open the cluster global configuration file in a text editor and add [ndbd]  sections corresponding to the 2 new data nodes. (We give these data nodes IDs 3 and 4, and assume that they are to be run on host machines at addresses 198.51.100.3 and 198.51.100.4, respectively.) After you have added the new sections, the contents of the config.ini  file should look like what is shown here, where the additions to the file are shown in bold type: 

[ndbd default] DataMemory = 100M IndexMemory = 100M NoOfReplicas = 2 DataDir = /usr/local/mysql/var/mysql-cluster [ndbd] Id = 1 HostName = 198.51.100.1 [ndbd] Id = 2 HostName = 198.51.100.2 [ndbd] Id = 3 HostName = 198.51.100.3 [ndbd] Id = 4 HostName = 198.51.100.4 [mgm] HostName = 198.51.100.10 Id = 10 [api] Id=20 HostName = 198.51.100.20 [api] Id=21 HostName = 198.51.100.21 

Once you have made the necessary changes, save the file. 

Step 2: Restart the management server.  Restarting the cluster management server requires that you issue separate commands to stop the management server and then to start it again, as follows: 

1. Stop the management server using the management client STOP  command, as shown here: 

ndb_mgm> 10 STOP Node 10 has shut down. Disconnecting to allow Management Server to shutdown shell> 

