Node states

The PureWeb server's Status page provide links that allow you to edit the state of a node (whether or not it is clustered, and whether or not it is active).

The table below summarizes the various possible node states.

Status Description
Clustered Nodes that are participating in the cluster. They redirect requests for new sessions to the least busy node in the cluster.
Unclustered Nodes that are not participating in the cluster. They do not redirect requests for new sessions to other nodes in the cluster.
Active Nodes that can accept requests for new sessions. They accept these requests if they are among the least busy nodes in the cluster.
Inactive Nodes that cannot accept requests for new sessions.

You can edit these states, for example to shut down a node or to test it.


Shutting down a node

To gracefully shut down an active, clustered node, first render it inactive (click on the Active link to change the status). This will redirect any requests for new sessions to another active, clustered node. Once all existing sessions have completed, mark it as unclustered (click on the Clustered link to change its status) so that it will not receive any further requests. You can now shut down the node without affecting any existing sessions.


Testing a node

To allow a node to be tested before it is brought into service, first configure it as unclustered but active and then start it for testing. Once testing is complete, shut down the node, reconfigure it as clustered and active, and then restart it to bring it into full service.

Note that changes made here are not persistent. When you restart the server, it uses the values in the cluster-plugin.xml file. For more information on this file, see Cluster configuration.