You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Brian Pane <bp...@pacbell.net> on 2001/08/08 22:01:07 UTC
graceful restart Re: Currently known issues with 2.0.23
Ryan Bloom wrote:
>>>>2) Unix: The threaded MPM might take longer than expected to restart or
>>>> shutdown on very-low-traffic (near idle) servers. This is due to
>>>>the
>>>>
>>>I dislike this. It's the "near idle" that bothers me. We rely on the
>>>OS to never starve a thread to get any restart or shutdown. The
>>>server could easily be getting hit moderately, and not shutdown
>>>correctly. I don't want to see us down-play the problem, and have
>>>people think that the server is working when it isn't. There is a
>>>real chance that an admin can do a graceful restart, and still be
>>>serving requests off the old config for a very long time.
>>>
>>How about "servers getting very few requests" instead of
>>"very-low-traffic (near idle) servers"?
>>
>>I threw the "near idle" bit in there to emphasize that (a) it effects
>>people running test servers that have nobody connecting to them at all,
>>and (b) that our definition here of "very low traffic" is not 100 conn/sec
>>as opposed to 1000 conn/sec, but more on the order of just a handful of
>>conn/sec, since 100 conn/sec might be seen as very low traffic by some
>>administrators. ;-)
>>
>
>a) is just not true. This doesn't affect only test servers, it affects anybody who
>isn't seeing a log of hits at a time. And we haven't got a clue what the threshold
>is. Again, we rely on the OS to make sure that every single thread gets
>the it's share of the connections.
>
Yep. And I think the 'server not getting many hits' case should be expected
even on high-traffic sites. A cautious operations team might reasonably do
something like this when making config changes:
- Configure the load balancer to stop sending new connections to one
of n web servers
- Install a new httpd.conf on that server
- Graceful restart of apache (to give any open connections a chance to
complete)
- Verify that the server handles requests as expected
- Configure the load balancer to start sending traffic to that server
again
--Brian
Re: graceful restart Re: Currently known issues with 2.0.23
Posted by Greg Ames <gr...@remulak.net>.
Brian Pane wrote:
> Yep. And I think the 'server not getting many hits' case should be expected
> even on high-traffic sites. A cautious operations team might reasonably do
> something like this when making config changes:
> - Configure the load balancer to stop sending new connections to one
> of n web servers
> - Install a new httpd.conf on that server
> - Graceful restart of apache (to give any open connections a chance to
> complete)
> - Verify that the server handles requests as expected
> - Configure the load balancer to start sending traffic to that server
> again
Not a problem, sir. AFAIK, threaded will handle this scenario just
fine.
Greg