Stop clusters
Use this task to stop a cluster and any appservers that are members of that cluster.
![[Windows]](../../windows.gif)
If you use the Windows Services facility to start and stop appservers that are part of a cluster, remember that the cluster state does not always update correctly. For example, if a cluster is running and you stop a cluster member through the Services GUI, the cluster state remains as Started even though the server is no longer running.
Overview
You can stop all appservers that are members of the same cluster at the same time by stopping the cluster.
Procedure
- Click Servers > Clusters in the console navigation tree
to access the Server
Cluster page.
- Select those clusters whose members you want stopped.
- 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 partially stopped. After all servers stop, the cluster state becomes 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 Partially stopped. After all servers stop, the cluster state becomes Stopped.
- 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 partially stopped. After all servers stop, the cluster state becomes Stopped.
What to do next
See Balancing workloads with clusters for more information about the tasks you can complete with clustering.Balancing workloads with clusters