Hi Remy,
Just a couple of comments.
1) As per your response, if DNS is down squid is not going to be much
happier as it needs that DNS resolution in order to be able to function ;-)
2) WCCP would/could work very nicely for you in a fully transparent
configuration. Cost of wccp capable routers plays a role
3) A true load balancer front end like Cisco's content director could
also do the job but also runs into cost issues.
Methods I've used:
1) Running squid in an LVS (linux virtual server) environment - works
but can get fun to configure
2) Add another squid box to the configuration.
- Setup this squid so that 10.200.1.2 and 10.200.1.1 are parent
caches with CARP enabled
- Do not enable any disk storage on this front-end cache
This gives you an environment where the parent caches will determine
load between them and handle requests as needed.
Setting dead_peer_timeout and peer_connect_timeout will also allow
relatively quick responses to caches that die.
I know this last option is not fully redundant but is a cost effective
way of handling the load balancing issue cleanly.
Regardt
Mario Remy Almeida wrote:
Hi All,
What I mean to say is..
E.G:-
SP 1 = 10.200.2.1
SP 2 = 10.200.2.2
LAN USERS = 10.200.2.x
All lan users should connect to SP1 or SP2 depending upon the load and
if one of the SP is down the other should take the load.
One way of achieving load balance is with DNS
proxy1.example.com IN A 10.200.2.1
proxy1.example.com IN A 10.200.2.2
And what if the DNS Server is down and also how to do fail over
//Remy
On Tue, 2008-12-23 at 09:05 -0600, Luis Daniel Lucio Quiroz wrote:
Just remember
when using load balancing, if you use digest auth, then you MUST use
source persistence.
On Tuesday 23 December 2008 08:38:27 Ken Peng wrote:
Hi All,
any links on how to configure load balancing of squid
See the default squid.conf, :)
