bugzilla at apache
Jul 21, 2008, 2:57 AM
Post #1 of 1
(122 views)
Permalink
|
|
[Bug 45445] New: Connection Timeout vs. Request Timeout in reverse balanced proxies
|
|
https://issues.apache.org/bugzilla/show_bug.cgi?id=45445
Summary: Connection Timeout vs. Request Timeout in reverse
balanced proxies
Product: Apache httpd-2
Version: 2.2.6
Platform: PC
OS/Version: Linux
Status: NEW
Severity: regression
Priority: P2
Component: mod_proxy_balancer
AssignedTo: bugs[at]httpd.apache.org
ReportedBy: federico.mennite[at]lifeware.ch
Up to the release of apache 2.2.4 the 'timeout' parameter of the BalancerMember
directive would affect only the connection timeout to the backend servers. This
allowed to set reasonably small timeout values(let's say 1 or 2 seconds) in a
scenario where the balancer and the backends would sit in the same LAN.
Starting from apache 2.2.6, it seems that the timeout value also affects the
backend request completion timeout.
Unfortunately some of our backend requests may take up to 10s to complete.
Increasing the timeout value to 15 seconds causes an annoying 'stall' behavior
when one of the backend servers becomes completely unreachable (e.g: power
failure).
I think it definitively makes sense to have both timeouts configurable
separately.
--
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe[at]httpd.apache.org
For additional commands, e-mail: bugs-help[at]httpd.apache.org
|
