stop processprocess_idcluster_name This command stops the running MySQL NDB Cluster process with the process IDprocess_id in the cluster namedcluster_name. The status of the process as shown byshow status--process must berunning.
Suppose that the process ID of a data node in the cluster namedmycluster is3. 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) You can useshow status--process orlist 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, ifStopOnError is set to 0, the MySQL Cluster Manager agent restarts the data node process automatically; ifStopOnError is 1 (the default), then you must execute thestart 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. SeeSection 4.4.1, “Thecreate cluster Command”, andSection 3.5, “Importing MySQL NDB Clusters into MySQL Cluster Manager”, for more information.