Stopping clusters

Use this task to stop a cluster and any application servers that are members of that cluster.

Why and when to perform this task

You can stop all application servers that are members of a cluster at the same time by stopping the cluster. You can stop all application servers in a server cluster at the same time.

When you start and stop application servers that are part of a cluster using the administrative console, the cluster state does not always update right away. For example, if a cluster is running and you stop a cluster member through administrative console, the cluster state remains as Started even though the server is no longer running.

Steps for this task

  1. Click Servers > Clusters in the console navigation tree to access the Server Cluster page.
  2. Select the clusters whose members you want stopped.
  3. Click Stop or Immediate Stop.
    • Stop halts each server in a manner that allows the server to finish existing requests and allows failover to another member of the cluster. When the stop operation begins the cluster state changes to websphere.cluster.partial.stop. After all servers stop, the cluster state becomes websphere.cluster.stopped.
    • Immediate Stop brings down the server quickly without regard to existing requests. The server ignores any current or pending tasks. When the stop operation begins, the cluster state changes to websphere.cluster.partial.stop. After all servers stop, the cluster state becomes websphere.cluster.stopped.

What to do next

See Balancing workloads with clusters for more information about the tasks you can complete with clustering.

Related tasks
Balancing workloads with clusters



Searchable topic ID:   trun_wlm_cluster_stop
Last updated: Jun 21, 2007 8:07:48 PM CDT    WebSphere Business Integration Server Foundation, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.wasee.doc/info/ee/ae/trun_wlm_cluster_stop.html

Library | Support | Terms of Use | Feedback