To access the Server Management page, go to Cluster Setup | Servers.
When first logging in to Zend Server, There will be no information displayed in the various tabs. Zend Server will start to collect information only after you have added at least one server to the cluster. The only exception to this is if you had servers running as a cluster and then removed them. All historical information in the Dashboard tabs is retained such as old queue statistics, jobs and trace information.
All subsequent information displayed in the Administration Interface represents the settings of the server defined as the master server. This is defined when the server was added by selecting the option "Configure all the cluster like this new server".
This procedure describes how to add a server to create a clustered environment that will be managed by Zend Server.
Once a server is added as a node you will no longer be able to login to the Zend Server Administration Interface that is running on the added server. All configuration and management actions will be done by Zend Server.
Before adding a node to the cluster, make sure that the server is running
Session Clustering.
When adding a server which has been removed using Graceful Shutdown back
to the cluster, make sure to only connect the server to your load balancing
pool after the servers list indicate that the server is in “Ok” status.
|
|
|
To add a server:
Note: If you do know what your password is, it may be because you installed Zend Server but never defined its password. To define the password, login to Zend Server and enter the password and license information.
|
The new server will be added to your cluster and will be shown in the Servers Status table in Monitor | Dashboard. |
Note:
You can only add servers running Zend Server 5.0 and above. All servers must be running the same version.
Disabling a server node is used when you would like to remove the node from the cluster, but not lose any of the Monitor and Code Tracing date. For example, before upgrading a node 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 node, 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 nodes during this process since some of the node's sessions are moved to other nodes. You may now carry out the relevant operations on the disabled server. For example, after disabling you can upgrade the node. |
Once you are done working with the machine you can enable the server. |
This procedure describes how to remove a server from your cluster.
|
|
|
To remove a server:
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. If this server was the master server, the next server in line will become the master after the server was removed. Once a server is removed as a node you will once again be able to login to the Zend Server Administration Interface that is running on the added server. All configuration and management actions will now be done by directly to the server. Configurations: Even if there were different configurations on the server before it was added to the cluster, after removing a node, the settings that were given to the node 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 (if there were previous settings to restore, if not the Zend Server's settings will stay). Session ClusteringThe "Remove Server" action 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 the "Remove" option for removing additional servers will not be available. Once the shutdown is completed you will be able to remove more servers. Job QueueWhen removing the node that
hosts the Job
Queue service, a special procedure is necessary.
Before removing the node you must go to Cluster
Setup | Job Queue and change the Default Job Queue Daemon
Address to a new node. This will ensure that all new jobs will
be sent to an enabled node where they can be carried out. |
The force remove option is available when a server cannot for some reason be removed from the cluster. This is normally the case when trying to remove the last node from a cluster or when the regular removal hangs for more than a minute. Force Remove releases the user interface on the node's side without performing any shutdown actions that preserve information such as graceful shutdown for session information. The other nodes in the cluster will stop communicating with nodes that have been removed with Force Remove
Important Note:
Before using Force Remove try to access the node you are trying to remove and see if you can locate the reason it could not be removed properly.
Enabling a server will make it an active node in the cluster. Before enabling a server, you must have disabled it.
|
|
|
To enable a server:
|
Note: The load will increase on active nodes during this process since some of the node's sessions are moved back to the enabled node. |
This procedure describes how to re-match a server. Re-match is the process of realigning the configurations on a given server that has different configurations. When this happens a notification will appear in Cluster Setup | Servers and a notice icon will appear next to the server's name.
Note:
Before re-matching a server check to see why the server's configurations changed in the first place.
|
|
|
To Rematch a server:
|
The Cluster manager's settings will be applied to the server. |
|
|
|
Related Links: Servers |
|
|
© 1999-2013 Zend Technologies, Ltd. All rights reserved.