Start and stop clusters

Start clusters

You can start all members of a cluster at the same time by requesting that the state of a cluster change to running. That is, you can start all application servers in a server cluster at the same time.

When you request that all members of a cluster start, the cluster state changes to Partial Start and each server that is a member of that cluster launches, if it is not already running. After all members of the cluster are running, the cluster state becomes Started.

To start a cluster and the application servers in that cluster, follow these steps:

  1. Start the administrative console.
  2. In the topology tree, expand Servers and click Clusters.
  3. On the Server Cluster page, select the cluster whose members you want to start.
  4. Click Start or RippleStart.

    • Start launches the server process of each member of the cluster by calling the node agent for each server to start the servers. After all servers are running, the status of the cluster changes to Started. If the call to a node agent for a server fails, the server will not start.
    • RippleStart combines stopping and starting operations. It first stops and then restarts each member of the cluster.

    Note: It may take several minutes for all of the cluster members to start. When you click Start, the status of the cluster changes to Partial Start until all of the cluster members are running.

Stop clusters

To stop a cluster and the application servers in that cluster, follow these steps:

  1. Start the administrative console.
  2. In the topology tree, expand Servers and click Clusters.
  3. On the Server Cluster page, select the clusters whose members you want to stop.
  4. 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 status changes to Partial Stop. After all servers stop, the cluster status becomes Stopped.
    • Immediate Stop brings down the server quickly without regard to existing requests. When the stop operation begins, the cluster status changes to Partial Stop. After all servers stop, the cluster status becomes Stopped.