Setting Up Clusters : Starting and Stopping the Cluster : Starting and Stopping Node Managers Using the Command Line Interface
 
Share this page                  
Starting and Stopping Node Managers Using the Command Line Interface
You can start a new node manager on a machine. The node is identified by the unqualified host name of the machine where the command is run. Alternatively, a name can be provided as an argument to the start-node command. Note that node names must be unique across the cluster.
To simplify node recovery, starting a node manager using an already registered node name replaces the existing node in the cluster.
Starting a node manager
[dataflow@galaxy ~]$ clustermgr start-node -cluster.host galaxy -cluster.port 1099
Node manager 'galaxy' starting
To shut down the cluster, use the stop-cluster command. This stops all daemon processes, starting with the node managers and then Cluster Manager.
Shutting down the cluster
[dataflow@galaxy ~]$ clustermgr stop-cluster -cluster.host galaxy -cluster.port 1099
Shutting down node galaxy@galaxy.englab.local...
Shutting down node saturn@saturn.englab.local...
Shutting down cluster manager galaxy.englab.local:1099...
Cluster shutdown
If only a single node must be removed from the cluster, use the stop-node command. This action shuts down the node manager on the machine where it is run. Providing a node name as an additional argument shuts down the specified node, which may be remote.
Shutting down a specific node
[dataflow@galaxy ~]$ clustermgr stop-node -node.name galaxy -cluster.host galaxy -cluster.port 1099
Setting Up Automatic Startup
To maintain a cluster, we recommend you configure the machines running a cluster daemon to automatically start them when the machine is started. To do this, you can script the required commands above and run them during system startup. For scripting options, see your operating system documentation.
Note:  Remember that the daemon processes should be started using a nonprivileged user, such as the account under which the DataFlow software was installed. On UNIX, startup scripts run under the superuser account. Use sudo -u along with the clustermgr command to start the daemons as a specific user.
A node manager can be started before Cluster Manager. If the node manager cannot contact Cluster Manager to register during initialization, then it will reattempt registration a number of times before ending. These attempts reduce the possibility of a race condition between Cluster Manager and the node manager.