5.6.5 The stop process Command

stop process nodespec cluster_name

nodespec:
    {nodetype | process_id_list}
process_id_list:
    process_id[, process_id[, ...]]

This command stops the MySQL NDB Cluster processes specified by nodespec in the cluster named cluster_name. The status of the processes to be stopped, as shown by show status --process, must be running.

Suppose that the process ID of a data node in the cluster named mycluster is 3. Then this data node can be stopped as shown here:

mcm> stop process 3 mycluster;
+------------------------------+
| Command result               |
+------------------------------+
| Process stopped successfully |
+------------------------------+
1 row in set (33.07 sec)

For MySQL Cluster Manager 8.0.31 and later: Instead of a single node, you can also specify the type of nodes or a list of nodes (must be of the same type) to be stopped. For example:

mcm> stop process mysqld mycluster;
+------------------------------+
| Command result               |
+------------------------------+
| Process stopped successfully |
+------------------------------+
1 row in set (15.70 sec)

mcm> stop process 146,147 mycluster;
+------------------------------+
| Command result               |
+------------------------------+
| Process stopped successfully |
+------------------------------+
1 row in set (3.82 sec)

You can use show status --process or list processes to obtain process IDs for all processes in a given cluster.

In the event of a disk failure where MySQL Cluster Manager loses its manager directory (including its repository), the agent is able to recover information from other agents, but it does not actually control processes any longer, although it can detect them. This is due to the fact that the MySQL Cluster Manager agent cannot access the PID files. In this case, stop process no longer works, and you must kill such processes manually. Keep in mind that, if StopOnError is set to 0, the MySQL Cluster Manager agent restarts the data node process automatically; if StopOnError is 1 (the default), then you must execute the start process command manually.

This command does not work with processes in a cluster created for import where the import has not yet actually been completed. See Section 5.4.1, “The create cluster Command”, and Section 4.5, “Importing MySQL NDB Clusters into MySQL Cluster Manager”, for more information.