https://bz.apache.org/bugzilla/show_bug.cgi?id=53555
--- Comment #67 from Thomas Jarosch <[email protected]> --- Hi Stefan, (In reply to Stefan Fritsch from comment #60) > > the patch from #55 seems to make things scale a lot better. > > Also the status output is very helpful. > > Glad to hear that and thanks for testing it. Sorry, I didn't see your reply as bugzilla didn't add me to CC: automatically. Which is rather odd since it's the default setting. Back to the topic: > > Probably GracefulShutdownTimeout will help here, may be > > having a default value of one hour might make sense > > for httpd in general? > > Currently the children won't honor GracefulShutdownTimeout. But that should > be added. very nice. > > Third option (preferred one): Have an own GracefulShutdownLimit > > that's separate from ServerLimit. If we have too many processes, > > start killing of oldest process from the graceful shutdown list. > > Process in graceful shutdown mode don't count for ServerLimit. > > Yes, we could do that, too. But first I need something like > GracefulShutdownTimeout to work for the old child processes. ok. In the meantime I've decreased the ServerLimit/ThreadLimit to 5 and increased the ServerLimit 160 and more. The results with these settings are very good, no more user complaints (see below). Otherwise those long running HTTP CONNECT sessions were still maxing out the total number of allowed processes. > If you have any more experiences with the patch I am certainly interested. > Even if it has simply run for some time without (new) bugs exposed. the patch had been deployed to about ~3.000 servers since November 2016 with different work loads from 10 users to 400+ users. After applying your patch + the ThreadLimit change, there were no more complaints :) I've also diffed httpd 2.4.23 + the patch with the version of the code that landed in 2.4.25 and it's exactly the same. I'm soon going to roll out 2.4.25 to those boxes. Thanks again! Thomas -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
