Intergraph WebScale User Manual page 37

WebScale™ User's Guide
the cluster will handle all of the traffic for this rule. The allowed values range from 1,
the highest priority, to the number of maximum hosts specified by your license key.
This value must be unique for all hosts in the cluster.
Multiple Hosts Filtering Mode
This parameter specifies that multiple hosts in the cluster will handle network traffic for
the associated port rule. This filter mode provides scaled performance in addition to
fault-tolerance by distributing the network load among multiple hosts. You can specify
that the load be equally distributed among the hosts or that each host handle a specified
load percentage.
Network traffic is distributed among the hosts on a per-connection basis for TCP (or a
per-datagram basis for UDP), where the combination of source IP address, and source
and destination port numbers determines a unique client request. The distribution
algorithm is optionally restricted when client affinity is selected to ensure that multiple
connections within a client session are handled by the same cluster host.
Affinity: None
The None button specifies that WebScale does not need to direct multiple requests from
the same client to the same cluster host (that is, no client affinity).
Enabling client affinity ensures that only one cluster host handles all connections that
are part of the same client session. This property is important if the server application
running on the cluster host maintains session state (such as "server cookies") between
connections. However, disabling client affinity improves performance because it allows
multiple connections from the same client to be simultaneously handled by different
cluster hosts. To maximize scaled performance, disable client affinity when it not
needed.
Affinity: Single
The Single button specifies that WebScale should direct multiple requests from the same
client IP address to the same cluster host.
Enabling client affinity ensures that only one cluster host handles all connections that
are part of the same client session. This property is important if the server application
running on the cluster host maintains session state (such as "server cookies") between
connections. However, disabling client affinity improves performance because it allows
multiple connections from the same client to be simultaneously handled by different
cluster hosts. To maximize scaled performance, disable client affinity (by clicking the
None button) when it is not needed.
You can optionally modify WebScale's client affinity to direct all client requests from a
TCP/IP Class C address range (instead of a single IP address) to a single cluster host by
33