content_image/866235.jpg content_image/866234.jpg
2010-06-23 07:53:34 [MgmtSrvr] INFO -- Reading cluster configuration from ’config.ini’ 

The management node process continues to print logging output to the console. This is normal, because the management node is not running as a Windows service. (If you have used NDB Cluster on a Unix-like platform such as Linux, you may notice that the management node’s default behavior in this regard on Windows is effectively the opposite of its behavior on Unix systems, where it runs by default as a Unix daemon process. This behavior is also true of NDB Cluster data node processes running on Windows.) For this reason, do not close the window in which ndb_mgmd.exe  is running; doing so kills the management node process. (See Section 23.2.2.4, “Installing NDB Cluster Processes as Windows Services” , where we show how to install and run NDB Cluster processes as Windows services.) 

The required -f  option tells the management node where to find the global configuration file ( config.ini ). The long form of this option is --config-file . 

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

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

## Important 

An NDB Cluster management node caches the configuration data that it reads from config.ini ; once it has created a configuration cache, it ignores the config.ini  file on subsequent starts unless forced to do otherwise. This means that, if the management node fails to start due to an error in this file, you must make the management node re-read config.ini  after you have corrected any errors in it. You can do this by starting ndb_mgmd.exe  with the --reload  or --initial  option on the command line. Either of these options works to refresh the configuration cache. 

It is not necessary or advisable to use either of these options in the management node’s my.ini  file. 

2. On each of the data node hosts, run the command shown here to start the data node processes: 

C:\mysql\bin> ndbd 2010-06-23 07:53:46 [ndbd] INFO -- Configuration fetched from ’localhost:1186’, generation: 1 

In each case, the first line of output from the data node process should resemble what is shown in the preceding example, and is followed by additional lines of logging output. As with the management node process, this is normal, because the data node is not running as a Windows service. For this reason, do not close the console window in which the data node process is running; doing so kills ndbd.exe . (For more information, see Section 23.2.2.4, “Installing NDB Cluster Processes as Windows Services” .) 

3. Do not start the SQL node yet; it cannot connect to the cluster until the data nodes have finished starting, which may take some time. Instead, in a new console window on the management node host, start the NDB Cluster management client ndb_mgm.exe , which should be in C:\mysql\bin  on the management node host. (Do not try to re-use the console window where ndb_mgmd.exe  is running by typing CTRL + C , as this kills the management node.) The resulting output should look like this: 

C:\mysql\bin> ndb_mgm -- NDB Cluster -- Management Client -- ndb_mgm> 

When the prompt ndb_mgm>  appears, this indicates that the management client is ready to receive NDB Cluster management commands. You can observe the status of the data nodes as they start by entering ALL STATUS  at the management client prompt. This command causes a running report of the data nodes’s startup sequence, which should look something like this: 

ndb_mgm> ALL STATUS Connected to Management Server at: localhost:1186 Node 2: starting (Last completed phase 3) (mysql-8.0.26-ndb-8.0.26) Node 3: starting (Last completed phase 3) (mysql-8.0.26-ndb-8.0.26) 

