Re: peerSelect problem

Serge Krashakov writes:

>Hi,
>
>I have squid-1.2.beta23 with all 4 patches compiled with --enable-icmp
>using 3 parent caches as closest-only.
>It seems that it doesn't consider RTT to neighbors when selecting
>the closest path.
>
>I have:
>
>Parent : squid1.osi.ru/3128/3130
>Flags : closest-only
>Address[0] : 195.178.193.139
>Status : Up
>AVG RTT : 19 msec
>
>Parent : sd.cache.nlanr.net/3128/3130
>Flags : closest-only
>Address[0] : 192.172.226.145
>Status : Up
>AVG RTT : 1231 msec
>
>Parent : lj.cache.nlanr.net/3128/3130
>Flags : closest-only
>Address[0] : 192.172.226.146
>Status : Up
>AVG RTT : 1269 msec
>
>and for example:
>
>152.2.254.0 10/ 10 1616.4 14.0 sunsite.oit.unc.edu www.sunsite.unc.e
du sunsite.unc.edu
> lj.cache.nlanr.net 71.6 7.0
> sd.cache.nlanr.net 71.7 7.0
> squid1.osi.ru 240.2 19.0
>
>but squid choose lj.cache.nlanr.net as CLOSEST_PARENT rather than squid1.osi.r
u:
>
>1998/08/14 13:09:31| peerSelect: ftp://sunsite.unc.edu/pub/Linux/apps/graphics
/
>1998/08/14 13:09:31| peerSelectFoo: 'GET sunsite.unc.edu'
>1998/08/14 13:09:31| peerCheckAlwaysDirectDone: 0
>1998/08/14 13:09:31| peerSelectFoo: 'GET sunsite.unc.edu'
>1998/08/14 13:09:31| peerSelectFoo: direct = DIRECT_MAYBE
>1998/08/14 13:09:31| peerSelect: CLOSEST_PARENT/lj.cache.nlanr.net
>1998/08/14 13:09:31| peerSelectCallback: ftp://sunsite.unc.edu/pub/Linux/apps/
graphics/
>
>Is it possible to improve selection policy?

Its supposed to work that way. Its selecting the neighbor which is closest
to the origin server. LJ is closer to unc.edu than osi.ru is.

If you don't want it to behave like that, try removing the closest-only option
from the cache_peer line.

Duane W.

--
wessels@nlanr.net                           Think Globally, Cache Locally.