You can define the same entry multiple times with round robin and this gives a percentage weight of requests.
This can be used for load balancing of different sized parents with various bandwidths. Example peer 3 peer 1 peer 3 peer 2 peer 3 peer 1 peer 3 2/7 requests to peer 1 1/7 requests to peer 2 This shall send 4/7 requests to peer 3 Hope this helps Further control can be gained by modifying the source. As far as I know (AFAIK) On Wednesday 14 July 2004 08:00 am, Merton Campbell Crockett wrote: > On Wed, 14 Jul 2004, Elsen Marc wrote: > > > During the last Millenium, we started using hierarchical Squid arrays > > > with load balancing. We are currently using Squid 2.4 STABLE7. > > > > > > We have been migrating to a new network architecture and have noticed > > > some problems with accessing the parent cache. This appears to be > > > > What are those problems, then ? > > Details, error messages e.d... > > The "detected DEAD parent/sibling" messages in the cache log. Squid > records multiple IP addresses for several siblings and the parent in an > array. The [0] element of the array may be the one with the longest delay > or unreachable. > > Is there a mechanism to define a preference order to IP addresses? > > Merton Campbell Crockett > > > M. > > > > > the result of Squid storing all IP addresses associated with a parent > > > or sibling cache. > > > > > > When queried, our DNS servers return the IP addresses in the preferred > > > order. Unfortunately, Squid stores the returned IP addresses but > > > doesn't maintain the ordering. > > > > > > Is there a mechanism within Squid for defining an IP address > > > sort list? > > > > > > Merton Campbell Crockett
