On Sun, 23 Jun 2013, Aleksey Chudov wrote:
> May be some connection on LVS Master erroneously considered non-persistent?
May be we can know more if we
grep ESTAB ip_vs_conn_sync
It will show SYNC or LOCAL. As for persistent
conns I assume they all are SYNC.
I see this:
- for some IPs from these 50 ESTABLISHED conns there are
persistent templates, some to same real server, others to
different real server
- there are only ESTABLISHED TCP conns, no other closing states
such as TIME_WAIT, etc. One option is the traffic to be
some outdated retransmissions with ACK bit. But this
can happen only if these ESTABLISHED conns are LOCAL in
Backup, if they are SYNC Master would assign them
real server by using the persistence scheduling. And
if they have assigned persistent template via cp->control,
they will not be synced when sync_persist_mode is 1.
So, may be only the SYNC/LOCAL flag can
give us more information.
Julian Anastasov <ja@xxxxxx>
To unsubscribe from this list: send the line "unsubscribe lvs-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html