Hi all,
Does anyone have any tips on how to fix this issue:
We've just moved to squid3 from squid2, and now when we do squid3 -k
reconfigure we get about 30 seconds of squid refusing/failing to
forward requests while it rejigs itself. I don't know if this is
squid3 rescanning the cache or doing something with squidguard (we
have a fairly complex+large squidguard setup)? I don't think this
happened with squid2.
What can we do to make this less noticeable?
- make it reconfigure faster?
- multiple squid servers - can we do failover somehow (either proxy
DNS record points to them both, or they automatically redirect (is
this what cache peers are for?))?
- go back to squid 2 - I didn't see any end user benefits of squid3
over squid2...
any help would be greatly appreciated.
thanks
Jim Potter
UK
Received on Mon Jul 02 2012 - 08:08:52 MDT
This archive was generated by hypermail 2.2.0 : Mon Jul 02 2012 - 12:00:02 MDT