https://bz.apache.org/bugzilla/show_bug.cgi?id=59656
Bug ID: 59656
Summary: PATCH: mod_fcgid: Immediate HTTP error 503 if the max
total process count is reached
Product: Apache httpd-2
Version: 2.4.20
Hardware: PC
URL: https://github.com/famzah/mod_fcgid/compare/2.3.9...ma
xnowait?diff=split&name=maxnowait
OS: All
Status: NEW
Keywords: PatchAvailable
Severity: normal
Priority: P2
Component: mod_fcgid
Assignee: [email protected]
Reporter: [email protected]
Hi all,
I'd like to propose a new configuration setting for "mod_fcgid". The source
code changes to review follow:
- The whole patch compared to version 2.3.9:
https://github.com/famzah/mod_fcgid/compare/2.3.9...maxnowait?diff=split&name=maxnowait
- The whole patch as a single file:
https://github.com/famzah/mod_fcgid/compare/2.3.9...maxnowait.patch?diff=unified&name=maxnowait
- Every single commit compared to version 2.3.9:
https://github.com/famzah/mod_fcgid/commits/maxnowait
- There should be no merge conflicts with the current "trunk" version 2.3.10.
The motivation is that the current behavior to queue up new pending requests
differs from the RLimitNPROC directive behavior. When there is a spike in the
web hits, lots of Apache children get busy just waiting for up to 30+ seconds
to get an idle FastCGI process. Thus we "waste" Apache children doing nothing
while they could serve static content. This also puts unneeded memory pressure.
Additionally, users today won't wait for a page to load, if it takes more than
a few seconds, and we'd rather notify them that we are currently overloaded by
sending them a 503 HTTP response immediately.
Here is the documentation for the new directive:
http://www.famzah.net/temp/FcgidMaxProcessesUsedNoWait.docs.txt
Let me know what you think.
Best regards.
--Ivan
--
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]
