Stopping clusters using the job manager

In a flexible management environment, we 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, we 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.

Use the admin 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, we can run the stopCluster job script in the AdministrativeJobs command group. See the Administrative job types topic.

 

1. Click Jobs > Submit from the navigation tree of the job manager administrative console.

2. Choose a job to stop a cluster.

   1. Select the Stop cluster job type from the list.

   2. Optionally specify a description of the job.

   3. Click Next.

3. Choose the job targets.

   1. Select a group of nodes from the list, or select Node names.

      Only groups of nodes that are valid for the job type that you selected are displayed in the list of groups of nodes.

   2. If you selected Node names, then specify a node name and click Add, or click Find and specify the chosen nodes on the Find nodes page.

   3. If user authentication is required, specify the user name and password.

   4. Click Next.

4. Specify parameters for the stop cluster job.

   1. For Cluster name, specify the name of cluster to stop. To see the names of existing clusters on the target nodes, click Find on the Specify job parameters page. On the Find node resources page, specify the target nodes and click Find. For example, suppose a managed node, myNode01, has a cluster named cluster2 to stop. Specify the name:

      cluster2
      

   2. Optionally, specify the maximum number of minutes to wait for the cluster to stop before returning the cluster state.

   3. Click Next.

5. Schedule the job.

   The times and dates that you specify are relative to the job manager.

   1. Optionally specify one or more e-mail addresses where notifications are sent when the job finishes.

      If you specify multiple e-mail addresses, separate them with commas.

   2. Select when the job is available for submission.

   3. Select the job expiration.

   4. Optionally specify a recurring interval for the job, a start date and time for the interval, and an end date and time for the interval.

   5. Click Next.

6. Review the summary, and click Finish to submit the job.

 

Results

The target nodes run the job and attempt to stop the cluster.

 

Next steps

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 Jobs > Node resources > resource_name to see the resource status.

After stopping the cluster, we can run the following jobs:

• Start cluster

• Delete cluster

---

Related tasks Set up a job manager environment Starting and stopping the job manager Starting and stopping the dmgr Starting and stopping a node Create clusters using the job manager Check job status Delete clusters using the job manager Starting clusters using the job manager Related reference Administrative job types using wsadmin scripting Find nodes Find node resources Node resources collection

   

---

Last updated Nov 10, 2010 8:23:07 PM CST