Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@httpd.apache.org
Message-ID: <20030205132905.47955.qmail@web12802.mail.yahoo.com>
Date: Wed, 5 Feb 2003 05:29:05 -0800 (PST)
From: Hans Zaunere <zaunere@yahoo.com>
Reply-To: hans@nyphp.org
Subject: Re: Graceful shutdown in 2.0
To: dev@httpd.apache.org
In-Reply-To: <3E40A863.7090903@sharp.fm>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii


--- Graham Leggett <minfrin@sharp.fm> wrote:
> David Burry wrote:
> 
> > um, but if you're talking about shutting down the proxy itself (i.e. the
> > whole service, cutting off all load balanced machines behind it) that's
> > hardly graceful to begin with.... so why bother to make it graceful...
> 
> If your proxy machines were being load balanced by an Alteon switch (or 
> whatever) you could probably tell the switch to stop sending new 
> connections to the proxy in question, while allowing the old connections 
> to finish. Of course this is based on whether the Alteon (or whatever) 
> config will let you do this of course.
> 
> On the proxy side, maybe some generic function in Apache that is not 
> proxy specific could signal Apache to go into a "disabled" state, where 
> new connections get "connection refused", while old connections run 
> their course. The load balancer I assume would detect this state and 
> pass any new requests on to other machines. You could use ./apachectl 
> disable and ./apachectl enable to achieve this.

I've wondered about this as well.  Even for just single servers, it'd be nice
to shutdown the server "gracefully".  Often, I'm more comfortable with
stopping and then starting the server than doing a reload, so a graceful
shutdown would be useful, unless I'm missing something that already exists.

Hans