I'm having an issue with the ActiveConn growing on a loadbalanced smtp
setup, it seems that the connection remains in the ESTABLISHED state
until it expires. Right now the traffic through this VIP is very low
for testing purposes but I intend to load balance our smtp gateway using
LVS and I'm afraid this will cause issues (approx 1.5 million emails per
day). I'm running 2.6.10-1.770_FC3smp on the real servers and the director.
Also, I'm loadbalancing smtp on port 10225 on a different set of servers
running 2.4.21-15.ELsmp and it doesn't exhibit this behavior.
I've seen this question posted before but haven't seen any answers.
Should I be concerned? Thanks for any advice.
IP Virtual Server version 1.2.1 (size=4096)
Prot LocalAddress:Port Scheduler Flags
-> RemoteAddress:Port Forward Weight ActiveConn InActConn
TCP 10.25.1.224:10225 rr
-> 10.25.19.64:10225 Tunnel 1 1 4
-> 10.25.19.62:10225 Tunnel 1 0 5
-> 10.25.19.61:10225 Tunnel 1 1 4
-> 10.25.19.65:10225 Tunnel 1 0 5
-> 10.25.19.66:10225 Tunnel 1 1 4
-> 10.25.19.63:10225 Tunnel 1 0 6
TCP 10.25.1.228:25 rr
-> 10.25.1.92:25 Tunnel 1 186 0
-> 10.25.1.85:25 Tunnel 1 180 0
IPVS connection entries
pro expire state source virtual destination
TCP 01:42 ESTABLISHED 10.25.1.242:56963 10.25.1.228:25 10.25.1.85:25
TCP 01:33 FIN_WAIT 10.25.1.92:57049 10.25.1.224:10225
10.25.19.65:10225
TCP 06:19 ESTABLISHED 10.25.1.244:47994 10.25.1.228:25 10.25.1.85:25
TCP 01:21 ESTABLISHED 10.25.1.246:56365 10.25.1.228:25 10.25.1.85:25
TCP 00:59 ESTABLISHED 10.25.1.243:45479 10.25.1.228:25 10.25.1.92:25
TCP 00:37 ESTABLISHED 10.25.1.244:56672 10.25.1.228:25 10.25.1.92:25
TCP 14:38 ESTABLISHED 10.25.1.242:33580 10.25.1.228:25 10.25.1.92:25
TCP 00:25 ESTABLISHED 10.25.1.243:58378 10.25.1.228:25 10.25.1.92:25
TCP 00:09 ESTABLISHED 10.25.1.244:43548 10.25.1.228:25 10.25.1.85:25
TCP 06:08 ESTABLISHED 10.25.1.245:50431 10.25.1.228:25 10.25.1.92:25
TCP 13:49 ESTABLISHED 10.25.1.246:33974 10.25.1.228:25 10.25.1.85:25
TCP 00:16 ESTABLISHED 10.25.1.244:55966 10.25.1.228:25 10.25.1.92:25
TCP 00:47 ESTABLISHED 10.25.1.243:36233 10.25.1.228:25 10.25.1.92:25
TCP 05:19 ESTABLISHED 10.25.1.246:58326 10.25.1.228:25 10.25.1.92:25
TCP 00:32 ESTABLISHED 10.25.1.245:54772 10.25.1.228:25 10.25.1.85:25
TCP 00:52 ESTABLISHED 10.25.1.241:58541 10.25.1.228:25 10.25.1.92:25
TCP 00:10 ESTABLISHED 10.25.1.244:44344 10.25.1.228:25 10.25.1.92:25
TCP 10:53 ESTABLISHED 10.25.2.102:2812 10.25.1.227:53 10.25.1.77:53
TCP 00:44 ESTABLISHED 10.25.1.246:59583 10.25.1.228:25 10.25.1.85:25
TCP 00:33 ESTABLISHED 10.25.1.242:35053 10.25.1.228:25 10.25.1.92:25
TCP 00:58 ESTABLISHED 10.25.1.241:51373 10.25.1.228:25 10.25.1.92:25
TCP 00:18 ESTABLISHED 10.25.1.246:36021 10.25.1.228:25 10.25.1.92:25
TCP 00:33 ESTABLISHED 10.25.1.245:54756 10.25.1.228:25 10.25.1.92:25
TCP 00:24 ESTABLISHED 10.25.1.244:47759 10.25.1.228:25 10.25.1.85:25
TCP 00:59 ESTABLISHED 10.25.1.241:49392 10.25.1.228:25 10.25.1.85:25
TCP 00:30 ESTABLISHED 10.25.1.246:55677 10.25.1.228:25 10.25.1.85:25
TCP 09:02 ESTABLISHED 10.25.1.243:52385 10.25.1.228:25 10.25.1.92:25
--
Joel Nimety
Perimeter Internetworking Corp.
203.541.3416
------------------------------------------------------------------------
This e-mail transmission may contain information that is proprietary,
privileged and/or confidential and is intended exclusively for the
person(s) to whom it is addressed. Any use, copying, retention or
disclosure by any person other than the intended recipient or the
intended recipient's designees is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
return e-mail and delete all copies.
|