Stop clusters
One can stop all members of a cluster at the same time by requesting that the state of a cluster change to stopped. That is, you can stop all application servers in a server cluster at the same time.
- Click Servers > Clusters in the console navigation tree to access the Server Cluster page.
- Put a checkmark in the check boxes beside 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 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. 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.
One can also stop and start server clusters from the settings page for a server cluster instance. To access such a page, click on the server cluster that you want to start or stop in the collection under Name on a Server Cluster page. One can view the status of a server cluster (that is, whether the cluster is started or stopped) on the Runtime tab of the settings page for a server cluster instance. Note that the Runtime tab is only shown if you have clicked Save on the administrative console taskbar since creating the server cluster instance.
Note to Windows users: If you start and stop appservers that are part of a cluster using the Windows Services facility, 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.
Balancing workloads with clusters
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.