Commands in the NDB Cluster Management Client Brings online the data node identified by  node_id  (or all data nodes). ALL START  works on all data nodes only, and does not affect management nodes. To use this command to bring a data node online, the data node must have been started using  --nostart  or  -n . Stops the data or management node identified by  node_id . ALL STOP  works to stop all data nodes only, and does not affect management nodes. A node affected by this command disconnects from the cluster, and its associated  ndbd  or  ndb_mgmd process terminates. The  -a  option causes the node to be stopped immediately, without waiting for the completion of any pending transactions. Normally,  STOP  fails if the result would cause an incomplete cluster. The  -f  option forces the node to shut down without checking for this. If this option is used and the result is an incomplete cluster, the cluster immediately shuts down. Use of the  -a  option also disables the safety check otherwise performed when STOP  is invoked to insure that stopping the node does not cause an incomplete cluster. In other words, you should exercise extreme care when using the  -a option with the  STOP  command, due to the fact that this option makes it possible for the cluster to undergo a forced shutdown because it no longer has a complete copy of all data stored in  NDB . Restarts the data node identified by  node_id  (or all data nodes). Using the  -i  option with  RESTART  causes the data node to perform an initial restart; that is, the node’s file system is deleted and recreated. The effect is the same as that obtained from stopping the data node process and then starting it again using  ndbd --initial  from the system shell. Backup files and Disk Data files are not removed when this option is used. Using the  -n  option causes the data node process to be restarted, but the data node is not actually brought online until the appropriate  START  command is issued. The effect of this option is the same as that obtained from stopping the data node and then starting it again using  ndbd --nostart  or  ndbd -n from the system shell. Using the  -a  causes all current transactions relying on this node to be aborted. No GCP check is done when the node rejoins the cluster. 4440 Note Warning Note Important • node_id  STOP [-a] [-f] • node_id  RESTART [-n] [-i] [-a] [-f]