Re: [squid-users] Squid takes too long to stop.

From: Ben Drees <ben@dont-contact.us>
Date: Fri, 08 Sep 2006 11:48:01 -0700

Hello,

I have a load balancer in front of two Squids in a reverse proxy setup.
The load balancer decides whether a Squid is healthy by opening a TCP
connection to it periodically. During the shutdown interval governed by
configuration parameter 'shutdown_lifetime', Squid 2.5 STABLE12
continues accepting connection requests and responding to each request
with status code 503. The load balancer interprets this as "healthy". I
would prefer instead that Squid continue servicing pending requests on
open connections, but refuse new connection requests so that the load
balancer could do its thing and route to the other Squid for
uninterrupted service. Is there any way to achieve this in Squid 2.5
STABLE12 or later?

Thanks,
Ben

Henrik Nordstrom wrote:
> fre 2006-08-25 klockan 09:24 -0700 skrev Jim John:
>
>> Hi all. We have squid set up for transparency using shorewall, but it takes
>> too long to stop. Can we simply direct traffic away from squid using
>> shorewall before we stop squid instead of afterwards?
>>
>
> Yes, assuming you are doing transparent interception using iptables NAT.
>
>
>> Is there another way
>> to stop squid faster and safer because our users lose connection while squid
>> is stopping, which takes 2 minutes or so.
>>
>
> See shutdown_lifetime.
>
>
>> This also happens for reload when we have squidGuard child processes running under squid. Thanks.
>>
>
> What is a "reload"?
>
> Squid know how to stop, start, rotate logs and reconfigure.
>
> Regards
> Henrik
>
Received on Fri Sep 08 2006 - 12:48:43 MDT

This archive was generated by hypermail pre-2.1.9 : Sun Oct 01 2006 - 12:00:03 MDT