Re: slab usage and ip_vs_conn expiration

[Mark de Vries <markdv.lvsuser@xxxxxxxxxx>]

On Fri, 6 May 2005, Mark de Vries wrote:

> On Fri, 6 May 2005, Julian Anastasov wrote:
>
> >     It looks like ip_vs_conn_expire detects unexpected cp->refcnt
> > or cp->n_control (not likely). So, only on higher load UDP conns are
> > not freed, are you sure that TCP conns are freed? I assume it is
>
> AFAICT yes.. There are also a few persisten TCP services on the box so
> there are some templates still there.. I'd have to wait a couple of hours
> to make sure they are also cleaned up... but so far this looks good.

OK. I checked again and all but 4 TCP enties have gone.

But the 4 that are left puzzel me (again)

lvs-dns1:~# ipvsadm -L -c -n | grep TCP
TCP 00:56  NONE        xxx.yyy.101.232:0  77.43:80 10.31.66.163:80
TCP 00:56  ESTABLISHED 101.232:1134 77.43:80 10.31.66.163:80
TCP 00:49  ESTABLISHED 117.21:1255 77.43:80 10.31.66.162:80
TCP 00:47  NONE        117.21:0   77.43:80 10.31.66.162:80

lvs-dns1:~# ipvsadm -L -c -n | grep TCP
TCP 00:00  NONE        101.232:0  77.43:80 10.31.66.163:80
TCP 00:01  ESTABLISHED 101.232:1134 77.43:80 10.31.66.163:80
TCP 00:54  ESTABLISHED 117.21:1255 77.43:80 10.31.66.162:80
TCP 00:51  NONE        117.21:0   77.43:80 10.31.66.162:80

lvs-dns1:~# ipvsadm -L -c -n | grep TCP
TCP 00:54  NONE        101.232:0  77.43:80   10.31.66.163:80
TCP 00:55  ESTABLISHED 101.232:1134 77.43:80 10.31.66.163:80
TCP 00:47  ESTABLISHED 117.21:1255 77.43:80 10.31.66.162:80
TCP 00:45  NONE        117.21:0   77.43:80  10.31.66.162:80

Why don't these transition state... I've watched these counters jump from
00:00 to 00:59 a couple of times now... Is that normal?

(This director is not active any more... No traffic for these IPs hits
this box. verified using tcpdump.)

Rgds,
Mark.