Specifications

Chapter 7: Monitoring Equalizer Operation
104 Equalizer Installation and Administration Guide
are the current, dynamically-adjusted values, not the static weights initially assigned by the
administrator.
• active: The number of current connections to the server.
• processed: The total number of connections that have been processed by the server since the
system was rebooted.
• sticky (Layer 4 clusters only): The number of “sticky records” currently held by Equalizer.
Each one of these represents a Layer 4 connection to an L4 TCP or UDP cluster with a non-
zero sticky time. See “Enabling Sticky Connections” on page 80.
For each site in a geocluster, the summary displays the following information:
• weight: The server weights determine the relative proportion of connection requests that
Equalizer routes to each server. If you have enabled automatic load balancing, these weights
are the current, dynamically-adjusted values, not the static weights initially assigned by the
administrator.
• times chosen: the number of times this site was selected by geographic load balancing to
respond to a client request.
• times down: the number of times this site was down when geographic load balancing was
attempting to select a site to respond to a client request. Note: this does not indicate current
site status. Current site status is indicated by the color of the site in the table: green indicates
up, red indicates it is down, and yellow indicates the site is a hot spare.
The cluster summary indicates the following server states:
• Servers shown in green are currently active.
• Servers shown in blue are quiescing, that is, handling current connections but not accepting
new ones.
• Servers shown in yellow are configured as hot spares.
• Servers shown in red are down. Equalizer monitors the status of active servers by periodically
probing the IP address and Port specified by the server endpoint. If these probes fail the
number of times specified by the strikeout threshold system parameter (see page 44), it
marks the server down, gives the server a weight of zero, and stops routing new requests to
that server. A server probe might fail even if the server machine is up and running. For
instance, if the HTTP server daemon fails on a server machine, Equalizer will refuse
connections to that endpoint.
Displaying Cluster Information
The cluster screen (see Figure 49) displays information about a cluster’s configuration. To display
the parameters for a cluster, follow these steps:
1. Log into the Equalizer Administration Interface in either view or edit mode.