You are currently viewing Zend Server 5.x documentation. Click here to view the latest Zend Server online documentation.

Managing Servers

 

To access the Server Management page, go to Cluster Setup | Servers.

Information Display

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".

Adding a 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.

 

 

Instructions on how to complete a procedure

To add a server:

  1. Go to Cluster Setup | Servers.
  2. Click Add Server.
    The server configuration page will open
  3. Enter the server's information as follows:
  • Server Name - a unique name for the server that will be used for identification purposes.

  • Zend Server Address -Complete the URL path to the Server you want to add by entering the server's IP address.

  • Server Password - the Administration Interface password you defined for accessing Zend 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.

  • Configure all the cluster like this new server - Select this option if you want to force-propogate the added server's settings throughout your cluster. If you do no select this option, the added server will inherit the Zend Server's settings.

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

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.

 

 

Instructions on how to complete a procedure

To disable a server:

  1. Remove the server you intend to shut down from your load balancing pool. This should be done following the recommended procedure depending on your load balancing configuration.
  2. Go to Cluster Setup | Servers.
  3. Go to the node you would like to disable and in its column click Disable.
    Click OK when a notification asking to confirm your decision is displayed.
  4. The server’s status should indicate that it is disabling. This process may take between a few seconds and a minute, depending on the number and size of sessions and on your network throughput.

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.

Removing a Server

This procedure describes how to remove a server from your cluster. If you are removing the node which hosts the Job Queue service, see Job Queue before performing this procedure.

 

 

Instructions on how to complete a procedure

To remove a server:

  1. Remove the server you intend to shut down from your load balancing pool. This should be done following the recommended procedure depending on your load balancing configuration.
  2. Go to Cluster Setup | Servers.
  3. Click Remove.
    The remove process performs a Graceful Shutdown to ensure your Session Clustering data is not lost.
  4. To remove the server click OK when a notification asking to confirm your decision is displayed.
    Refresh the Servers list. If the server is no longer listed, it has been successfully removed.

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 Clustering

The "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 Queue

When 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.
Once you remove the node, all recurring jobs and jobs in the queue will be removed. It is highly recommended to allow any jobs in the queue to finish before continuing the removal process of the node. Recurring jobs must be re-added manually after the new node is hosting the Job Queue service.

Force Remove

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

Enabling a server will make it an active node in the cluster. Before enabling a server, you must have disabled it.

 

 

Instructions on how to complete a procedure

To enable a server:

  1. Go to Cluster Setup | Servers.

  2. Go to the node you would like to enable and in its column click Enable.

  3. Once the Administration Interface indicates that the server has been enabled, return it to your load balancer/ This should be done following the recommended procedure depending on your load balancing configuration.

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.

Re-matching a Server

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.

 

 

Instructions on how to complete a procedure

To Rematch a server:

  1. Go to Cluster Setup | Servers.
  2. Click Rematch Server.

The Cluster manager's settings will be applied to the server.

 

 

Related Links

Related Links:

Servers

 

 

 

© 1999-2013 Zend Technologies, Ltd. All rights reserved.