Re: [squid-users] cache_peer configuration

NP: please use the reply-to-list or reply-to-all feature of your
emailer. New threads for every post destroys visibility in the archives
and for those of us working with threaded email handling.

On 27/05/11 15:51, senthil kumar wrote:
> Hello Amos,
>
> Thanks for your reply.
>
> As you suggested i will use ICP or HTCP.
>
> Is it necessary to use round-robin in sibling ?

necessary? no.

I'm not aware of it having any effect on siblings actually. There is
ROUNDROBIN_PARENT peering type selection, but no round-robin sibling.

ICP/HTCP should override that by producing a fast responding sibling
which has a matching object.

>
> Based on the porxy1 config, If a client in 172.16.1.0/24 range makes a
> request and the requested object is not found in any of sibling
> servers,
> In the case the request will be forwarded via parent peer or as a
> direct request?

parent first, then DIRECT of that fails.

>
> proxy1 configuration:
> client range: 172.16.1.0/24 and 10.0.0.0/8
>
> cache_peer proxy2 sibling 3128 3130 proxy-only round-robin
> cache_peer proxy3 sibling 3128 3130 proxy-only round-robin
> cache_peer proxy4 sibling 3128 3130 proxy-only round-robin
> cache_peer proxy5 sibling 3128 3130 proxy-only round-robin
>
> cache_peer example.com parent 3128 7 no-query no-digest default name=filter
>
> acl peer src 172.16.1.0/24
> cache_peer_access filter allow peer
>
> Thanks,
> Senthil
>

Amos

-- 
Please be using
   Current Stable Squid 2.7.STABLE9 or 3.1.12
   Beta testers wanted for 3.2.0.7 and 3.1.12.1