Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 42547 invoked by uid 500); 23 Apr 2001 04:27:24 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 42440 invoked from network); 23 Apr 2001 04:27:20 -0000 Sender: gregames@Mail.MeepZor.Com Message-ID: <3AE3AEA7.154AC991@remulak.net> Date: Mon, 23 Apr 2001 00:25:11 -0400 From: Greg Ames X-Mailer: Mozilla 4.75 [en] (X11; U; Linux 2.2.17-21mdk i686) X-Accept-Language: en MIME-Version: 1.0 To: new-httpd@apache.org Subject: Re: Suggested direction for fixing threaded mpm thread startup. References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: h31.sny.collab.net 1.6.2 0/1000/N rbb@covalent.net wrote: > > On Sun, 22 Apr 2001, Greg Ames wrote: > > > Bill Stoddard wrote: > > > > > > > > > > > AFAIK, Paul hit this problem because of idle_server_maintenance and/or > > > > MaxRequestsPerChild - true? If that's really the extent of it, I > > > > believe there's a pretty easy solution. > > > > > > > > > > If you buy that, then why doesn't that solution work for > > > > MaxRequestsPerChild as well? > > > > > > > > True (IMHO). > > > > > > > For the low end folks it's probably the default anyway, which we > > > > developers just pulled out of the air. So if we have our mixed workload > > > > process basket case scenario going on, just hold off on killing any more > > > > processes until the first one terminates completely. > > > > > > Show us some code :-) > > > > > > > OK, it's committed...works swell for me. Paul? > > Um... This is an incredibly dangerous change. This makes Apache shutdown > one threaded process at a time. I think we have all downloaded tarballs > that are hundreds of megs, which can take a few hours to download. What > happens if while my server is serving one of those files, I need to do a > graceful restart to re-config my server. If the first process shutdown is > the one with the thread serving a three hour request, then my server won't > actually restart for 3 hours. > It doesn't affect any operator initiated shutdown/restart commands, only internal algorithmically generated things like perform_idle_server_maintenance and MaxRequestsPerChild. That said, there's something wrong with it. Processes with no worker threads were hanging around forever, like before the fix to do the joins. So I just disabled it. Greg