Re: Re: cache-digest against failover

Hi Alex

The child has recognized it upon the cache.log from the child:

1999/03/05 17:30:58| Detected DEAD Parent: yom.test.ubs.com/8080/3130
1999/03/05 17:31:18| TCP connection to yom.test.ubs.com/8080 failed

It's just our guess that the requests are due to digests cause of the
FAQ:
http://squid.nlanr.net/Squid/FAQ/FAQ-16.html#ss16.2
Cache servers periodically exchange their digests with each other
When a request for an object (URL) is received from a client a cache can
use digests from its peers to find out which of its peers (if any) have
that object. The cache
can then request the object from the closest peer (Squid uses the NetDB
database to determine this).

That's the reason why we think the child make these requests...
In my opinion the message "Detected DEAD Parent..." should disable that
the child looks up the entry in this table(if it really does)

Cheers

Pascal

rousskov@nlanr.net wrote:
>
> On Fri, 5 Mar 1999, pascal tscharner wrote:
>
> > we've got some children and a couple of parents.
> > the cache-digest has been enabled on the child-squids.
> > on each child we've defined 2 parents with different weigths.
> > if one parent is killed the child recognizes its death but he is still
> > trying to access the killed parent cause of the cache-digest entries.
>
> This should not be happening. Unless there is a bug, digests are not used
> for invalid parents. How do you know that the child recognizes parent's
> death? What makes you think that requests to a dead parent are due to
> digests?
>
> Thanks,
>
> Alex.