|
I am a little confused about the connection tracking in IPVS.
What I need is a 1 to 1 mapping from client IP to realserver IP. This
is for HTTP access for websites that need sessions maintained at the
load-balancer level.
I have one such customer's site that has a session timeout of 1h30m
(5400 sec).
My problem is with this customer's site .. we're seeing clients who
don't get stuck to one realserver, and I haven't been able to figure
out why.
% ipvsadm -lnc | grep CLIENT-IP
[...]
TCP 01:49 ESTABLISHED CLIENT-IP:4152 VIP:80 RIP2:80
TCP 00:40 ESTABLISHED CLIENT-IP:2221 VIP:80 RIP1:80
[...]
This shouldn't happen, should it?
I really don't need client ports (or destination ports, for that
matter) tracked at all, and it seems like there should be a way to do
it this way (which could also save some space..). For example, load
balancing on Riverstone gear allows you to choose a persistence level:
tcp - (client IP:Port -> VIP:Port)
ssl - (client IP -> VIP:Port)
sticky - (client IP -> VIP)
(there are a few others, but I've never used them)
--
Casey Zacek
Senior Engineer
NeoSpire, Inc.
|
