In a flexible management environment, you can submit the Stop cluster job to stop a running cluster that is on a managed node of the job manager.
Start the job manager if it is not running already.
To submit the Stop cluster job, the deployment manager node on which the cluster resides must be a managed node of the job manager. The cluster must be running.
Your ID at the job manager must be authorized for the administrator role or the operator role to submit jobs. When you submit a job, you can specify a user name and password for authentication and authorization at the target node or nodes. When you submit a job to multiple target nodes, the user name and password or the credentials for the submitter must be applicable to all the job targets.
You can use the administrative console of the job manager to stop clusters on one or more managed nodes. From the job manager console, choose the Stop cluster job, specify job options, review the summary, and submit the job.
Instead of using the job manager console, you can run the stopCluster job script in the AdministrativeJobs command group. See the Administrative job types topic.
The target nodes run the job and attempt to stop the cluster.
On the Job status page, click the ID of the stop cluster
job and view the job status. Click the status refresh icon to refresh the displayed status.
If the job is not successful, view any error messages that result from running the job, correct the error condition, and submit the job again.
If the job is successful, the status on the Node resources page of the cluster is Stopped. Click
to see the resource status.After stopping the cluster, you can run the following jobs:
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |