DROP NODEGROUP  acts only to remove the data nodes in the effected node group from that node group. It does not stop data nodes, assign them to a different node group, or remove them from the cluster’s configuration. A data node that does not belong to a node group is indicated in the output of the management client SHOW  command with no nodegroup  in place of the node group ID, like this (indicated using bold text): 

id=3 @10.100.2.67 (8.0.26-ndb-8.0.26, no nodegroup ) 

DROP NODEGROUP  works only when all data nodes in the node group to be dropped are completely empty of any table data and table definitions. Since there is currently no way using ndb_mgm  or the mysql  client to remove all data from a specific data node or node group, this means that the command succeeds only in the two following cases: 

1. After issuing CREATE NODEGROUP  in the ndb_mgm  client, but before issuing any ALTER TABLE ... REORGANIZE PARTITION  statements in the mysql  client. 

2. After dropping all NDBCLUSTER  tables using DROP TABLE . 

TRUNCATE TABLE  does not work for this purpose because this removes only the table data; the data nodes continue to store an NDBCLUSTER  table’s definition until a DROP TABLE  statement is issued that causes the table metadata to be dropped. 

For more information about DROP NODEGROUP , see Section 23.5.7, “Adding NDB Cluster Data Nodes Online” . 

• PROMPT [ prompt ] 

Changes the prompt shown by ndb_mgm  to the string literal prompt . 

prompt  should not be quoted (unless you want the prompt to include the quotation marks). Unlike the case with the mysql  client, special character sequences and escapes are not recognized. If called without an argument, the command resets the prompt to the default value ( ndb_mgm> ). 

Some examples are shown here: 

ndb_mgm> PROMPT mgm#1: mgm#1: SHOW Cluster Configuration ... mgm#1: PROMPT mymgm > mymgm > PROMPT ’mymgm:’ ’mymgm:’ PROMPT mymgm: mymgm: PROMPT ndb_mgm> EXIT jon@valhaj:~/bin> 

Note that leading spaces and spaces within the prompt  string are not trimmed. Trailing spaces are removed. 

• node_id  NODELOG DEBUG {ON|OFF} 

Toggles debug logging in the node log, as though the effected data node or nodes had been started with the --verbose  option. NODELOG DEBUG ON  starts debug logging; NODELOG DEBUG OFF  switches debug logging off. 

Additional commands.  A number of other commands available in the ndb_mgm  client are described elsewhere, as shown in the following list: 

