Re: TCP_SWAPFAIL_MISS and asyncufs/2.3

Chris Miles wrote:
 
> 2000/04/05 02:32:45| WARNING: swapin MD5 mismatch
> 2000/04/05 02:32:45| storeClientReadHeader: URL mismatch
> 2000/04/05 02:32:45| {http://www.asianmail.org/dt/dir.gif} != {http://209.132.206.17/vvtour/images/tours1_r4_c2.gif}

Squid thought it had one object in the file, found another.

> Q's:
> 1. TCP_SWAPFAIL_MISS means squid thought it had the object but cannot
> retrieve it from the cache. Why would this be happening (especially on a
> fresh cache)?

Some might happen, but you should not see a lot of them.

> 2. Are 2.2 and 2.3 cache spools supposed to be compatible? (and does
> asyncufs make any difference to compability?)

They are supposed to be backwards compatible (2.3 can use a 2.2 cache).

> 3. is asyncio stable enough under 2.3? squid performance appears to be
> much improved with it, only problem is the hit rates.

I don't think async-io is stable in Squid-2.3. It wasn't very stable in
the distributed Squid-2.2.STABLE5 version, and the implementation in
Squid-2.3 is in many aspects worse.

--
Henrik Nordstrom
Squid hacker
http://squid.sourceforge.net/squid/