content_image/671992.jpg content_image/671988.jpg
NodeId = 11 HostName = 198.51.100.151 [api] NodeId = 20 HostName = 198.51.100.200 [api] NodeId = 21 HostName = 198.51.100.201 

Assume that you wish to start this cluster using only the management server having node ID 10  and running on the host having the IP address 198.51.100.150. (Suppose, for example, that the host computer on which you intend to the other management server is temporarily unavailable due to a hardware failure, and you are waiting for it to be repaired.) To start the cluster in this way, use a command line on the machine at 198.51.100.150 to enter the following command: 

shell> ndb_mgmd --ndb-nodeid=10 --nowait-nodes=11 

As shown in the preceding example, when using --nowait-nodes , you must also use the --ndb- nodeid  option to specify the node ID of this ndb_mgmd  process. 

You can then start each of the cluster’s data nodes in the usual way. If you wish to start and use the second management server in addition to the first management server at a later time without restarting the data nodes, you must start each data node with a connection string that references both management servers, like this: 

shell> ndbd -c 198.51.100.150,198.51.100.151 

The same is true with regard to the connection string used with any mysqld  processes that you wish to start as NDB Cluster SQL nodes connected to this cluster. See Section 23.3.3.3, “NDB Cluster Connection Strings” , for more information. 

When used with ndb_mgmd , this option affects the behavior of the management node with regard to other management nodes only. Do not confuse it with the --nowait-nodes  option used with ndbd  or ndbmtd  to permit a cluster to start with fewer than its full complement of data nodes; when used with data nodes, this option affects their behavior only with regard to other data nodes. 

Multiple management node IDs may be passed to this option as a comma-separated list. Each node ID must be no less than 1 and no greater than 255. In practice, it is quite rare to use more than two management servers for the same NDB Cluster (or to have any need for doing so); in most cases you need to pass to this option only the single node ID for the one management server that you do not wish to use when starting the cluster. 

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

• --print-defaults 

## Note 

When you later start the “missing”  management server, its configuration must match that of the management server that is already in use by the cluster. Otherwise, it fails the configuration check performed by the existing management server, and does not start. 

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

Print program argument list and exit. 

