[squid-users] preventing 'DEAD parents'

hi,

a lot of questions again...

when using squid in a distributed infrastructure with squid boxes that are
connected
to their parent via wan connections, i sometimes have squid processes that
report
'detected DEAD parent', although the parent is reachable.
i guess this is caused by heavy wan traffic at a certain point of time, but
unfortunately
squid always takes a lot of time to recover until it detects its revived
parent then.

is it possible to disable the timeouts for child <-> parent communication
and thus,
stopping squid from complaining about dead parents?

what exactly does the 'default' tag mean for the cache_peer parameter?
i understood that i should use a 'default' parent as a last-resort parent.
will this
last-resort-parent be preferred over other parents with similar 'weight=xx'
values?

the configuration for my remote squid boxes is like this:

cache_peer central parent 3128 3130 weight=50
cache_peer backup parent 3128 3130 weight=20

maybe should i disable icp communication and do something like this:

cache_peer central parent 3128 7 no-query weight=50 default
cache_peer backup parent 3128 7 no-query weight=20 (default?)

please help.
thanks in advance
torsten

btw: some internet caching sites recommend using cache digests rather than
icp anyway.
what do you think?
Received on Mon Jun 18 2001 - 03:51:42 MDT