Quick update: we found the issue thanks to David's hint and solved the problem. That was exactly our problem. The real servers were using the default value for net.ipv4.tcp_keepalive_time which is 72
How long do these TCP connections live for? Perhaps they are sitting there with no packets for 15mins (or whatever the TCP timeout is on LVS in your configuration). Based on the timers of the 3 you w
As far as I know, there's no healthcheck being done from the client to the server. However, this may be built into the client software and I'm just not aware of it. To provide more context: * the cli
Do you perhaps have a health checker of some sort running that could account for the two connections? (Two LVS w/ keepalived, etc will look exactly like what you have shown.) -- _____________________
Hi list, I am seeing some odd connection behaviour between LVS and clients. I regulary see that the client->LVS connection count is higher from the client side than when I look at it on the LVS. For