Coyote Point Systems E350GX, Руководство по установке и администрированию

Страница: 116 / 344

Chapter 6: Administering Virtual Clusters
116 Equalizer Installation and Administration Guide
Layer 7 Persistence Tab
Please see “Enabling Persistent Server Connections” on page 129 for a discussion of server persistence on Equalizer.
cookie age
The cookie age sets the time, in seconds, over which the client browser
maintains the cookie (0 means the cookie never expires). After the specified
number of seconds have elapsed, the browser deletes the cookie and any
subsequent client requests will be handled by Equalizer’s load-balancing
algorithms.
cookie scheme
Specifies the format of the cookie to be used for the cluster as an integer
between 0 and 2 (default is 2)
0
Constructs a cookie which will be named in such a way that so as long as
the cluster maintains the same IP address, servers can be added to and
removed from the cluster without invalidating all of the existing cookies.
This cookie stores the cluster IP and port, and the server IP and
port.
1
Constructs a cookie which will be valid across all clusters with the same IP
address (not port specific). A requirement for this to be useful is that all
clusters on that IP address share the same set of servers.
This cookie
stores the Cluster IP, and Server IP and port.
2
Constructs a cookie which will be valid across all clusters with the same IP
address (using any port), and the same server within those clusters (with
the server using any port). A requirement for this to be useful is that all
clusters on that IP address share the same set of servers.
This cookie
encodes the Cluster IP and Server IP.
cookie generation
A value added to cookies when the cookie scheme is 2. In order for cookies to
be valid, the specified
cookie generation must match the equivalent number
embedded in the cookie. Conversely, if you need to invalidate old cookies,
increment this number.
cookie domain
If a cookie domain is specified, then Equalizer will honor cookies in client
requests only if the server’s host name is within the specified domain. For
example, if the cookie domain is
coyotepoint.com
, then Equalizer will only
present the cookie to servers in the
coyotepoint.com
domain (for example,
www.coyotepoint.com
or
my.coyotepoint.com
). Wildcards are not supported
in the cookie domain.
cookie path
If a cookie path is specified, Equalizer honors cookies in a client requests
only when the path component of the request URI has the same prefix as that
of the specified
cookie path . For example, if the cookie path is
/store/
,
Equalizer presents the cookie to the server only if the request URI includes a
path such as
/store/mypage.html
.
persist
When enabled (the default), Equalizer uses cookies to maintain a persistent
session between a client and a particular server. Equalizer “stuffs” a cookie
into the server’s response header on its way back to the client. This cookie
uniquely identifies the server to which the client was just connected. With
persist enabled, Equalizer routes only the first request from a client using
load balancing criteria; subsequent client requests are routed to the same
selected server for the entire session (while the cookie is valid -- see
cookie
age , above).
always
By default, Equalizer inserts a persistence cookie into a server response only
if it finds a cookie from the server in the response. If
always and persist are
enabled, Equalizer includes a cookie in the response regardless of whether the
server sent a cookie.
Note
: this option is listed as ‘
persist always
’ on match
rule
Configuration
tabs.