Managing Servers in a Cluster
Cluster management actions are performed from the Servers | Manage Servers page in the Zend Server UI, and allow you to quickly add, remove, enable and disable servers in a cluster.
For more information on working with a Zend Server cluster, watch this video:
This procedure describes how to change a server's name.
|
|
|
To edit a server:
|
|
Disabling a server is used when you would like to remove the server from the cluster, but not lose any of the Monitor and Code Tracing data. For example, before upgrading a server you must disable it. During the disabling process a Graceful Shutdown is performed to ensure your Session Clustering data is not lost.
If you would like to permanently remove a server, in which case all Session Clustering data will be lost, see Removing a Server.
|
|
|
To disable a server:
Note: The load will increase on active servers during this process since some of the server's sessions are moved to other cluster members. |
|
Enabling a server will make it an active server in the cluster. To be enabled, a server needs to be disabled.
|
|
|
To enable a server:
|
Note: The load will increase on active servers during this process since some of the server's sessions are moved back to the enabled server. |
This procedure describes how to remove a server from your cluster.
|
|
|
To remove a server from the cluster:
Note: If you plan to remove more than one server, repeat this process for each server after receiving confirmation that the previous server has been removed. Shutting servers down one by one is required to ensure information consistency. While a server is being removed you will not be able to add, edit or remove any other servers. |
The server will still be listed in the table but will no longer belong to the cluster. Once a server is removed, you will once again be able to login to the Zend Server UI that is running on the server. All configuration and management actions will now be done directly from the server. ConfigurationsEven if there were different configurations on the server before it was added to the cluster, the settings that were given to the server as part of a cluster will stay the same even after it was removed. The one exception to this are the Zend Monitor settings which will be restored to the server after it was removed. Session ClusteringRemoving a server from the cluster initiates a Graceful Shutdown process whereas all the active sessions will be rerouted to the other servers in the cluster. While the graceful shutdown is running, removing additional servers in the cluster is impossible. Once the shutdown is completed, you will be able to remove more servers. |
The Force Remove option is made available when a server cannot for some reason be removed from the cluster. This is normally the case when trying to remove the last server from a cluster or when the regular removal hangs for more than a minute. Force Remove releases the user interface on the server's side without performing any shutdown actions that preserve information such as graceful shutdown for session information. The other servers in the cluster will stop communicating with servers that have been removed with Force Remove.
Tip:
Before using Force Remove, try to access the server you are trying to remove and see if you can locate the reason it could not be removed properly.
|
|
|
To force remove a server from the cluster:
Note: If you plan to remove more than one server, repeat this process for each server after receiving confirmation that the previous server has been removed. Shutting servers down one by one is required to ensure information consistency. While a server is being removed you will not be able to add, edit or remove any other servers. |
This procedure describes how to restart servers in a clustered environment. You have the option to restart all your cluster, or select which servers to restart. The restart is executed according to the Restart Strategy defined on the Administration | Settings page.
|
|
|
To restart servers in your cluster:
Note: This type of restart will perform a full server restart. For more information, see Server Restart. |
|