Re: [squid-users] round-robin and lack of load balancing thru icp problem

the main problem arises with streams+large files, which can't be splitted in
both cases.
i tried other solution too.

On Thursday 03 July 2003 01:50, Adam Aube wrote:
> >adding such option to squid would be trivial, and greatly improve
>
> setups
>
> >where multiple ISP lines are available. there could be
> >round-robin-bond=[weight]
> >and 'algorithm' would be to measure incoming data rate, multiply
>
> it by number
>
> >of total weights , and do an icp query of next peer cache available
>
> for RETR
>
> >with this offset, proportional to it's weight, then move to next one.
> >offsets could be updated as the data flows...
>
> A better solution might be to use iproute2. Have all the Internet
> connections come into a single Squid box, then have the other two
> use the first as a parent. Setup iproute2 on the parent to load balance
> and failover with the Internet connections.
>
> You can then setup round-robin DNS for the child caches and have
> the clients use host names, not IP addresses, to connect. This will
> load balance the child caches.
>
> I have never actually done this, but searching for "Linux advance
> routing howto" and "Linux round robin DNS" should give you enough
> info to get you started.
>
> Adam

-- 
--