Red Hat Bugzilla – Bug 466205
Request backporting of Apache 2.2.6 internal dummy connection -handling
Last modified: 2008-10-09 04:21:15 EDT
Description of problem:
Under heavy (or moderate) load on a server serving dynamic web pages Apache's internal requests may consume all available Apache resources.
Version-Release number of selected component (if applicable):
difficult to reproduce, we ran 8 months without any problems
Steps to Reproduce:
1. set up a web-server with dynamic content
2. put it under stress /w hundreds of child-processes running simultaneously
3. watch legitimate client requests fight with Apache's internal requests
Site slowing down considerably. Internal requests stop only after Apache's Timeout-directive (RHEL default 120 seconds). Scoreboard has lot of Apache processes in "Sending Reply" -state. These hang up processes consume other resources too (DB-handles, etc.).
Smoothly running site with fast response time for legitimate users. No system resources wasted on Apache's own clumsiness.
The problem can be defeated using a couple of mod_rewrite -directives separating internal requests from others and telling them to "take a hike".
However, this is a gum/glue/duct tape workaround to save system resources. The problem in Apache does not go away by looking into another direction.
Thanks for the request. This is already scheduled to be fixed in the next update by switching to use of "OPTIONS *" rather than "GET /" in the dummy request.
*** This bug has been marked as a duplicate of bug 367981 ***