On Tue, 12 Jul 2011 13:31:54 +0200, Peter Olsson wrote:
On Tue, Jul 12, 2011 at 11:05:45AM +0000, Jenny Lee wrote:
> > How can you expect *machineS* to get a response from squid if
network is down?
>
> Proxy server. Squid accepts clients on inside interface and
> connects to internet servers on outside interface.
> Outside interface goes down with inside interface still alive.
>
> I would actually like to have the problem/feature below, since
> that would mean no clients get stuck at the nonfunctioning squid
> instead of moving to the next squid in the roundrobin failover.
If you read the original post, he mentions squid terminating when
network goes down.
Yes. I have had the case that the outside interface is
nonfunctioning, but squid is still up and accepts clients
on the inside interface. Squid then becomes a black hole
for client traffic, so I would prefer a terminating squid
in that case.
Configuring the layer as siblings can help with this case. The
black-holed requests get some extra lag going through two or more of the
siblings trying to find a good path or even just a cached stale result.
Not great, but better than nothing.
No clients get stuck at the nonfunctioning squid in a
cache-hierarcy. They would move on to the next one as is, since that
one is already marked as dead and removed from roundrobin pool. So
that feature is built-in already (if I am not misunderstanding your
scenario).
No cache-hierarchy, just several redundant squid servers on
the same level. Roundrobin is handled by internal DNS, which
has multiple A-records for the hostname "proxy".
Uhm. That would be a 1-layer hierarchy with round-robin LB.
Amos
