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.
Created attachment 22318 [details] Allow request timeout to be set separate from connection timeout for proxies This is used thus ProxySet timeout=30 requesttimeout=5 the connection timeout is set to 30, and the timeout for socket io is set to 5
Committed a slightly modified version of the patch as r684341 (http://svn.apache.org/viewvc?rev=684341&view=rev) to trunk. It introduces a 'connectiontimeout' that sets the timeout for the connect call with 'timeout' being the default.
I successfully tested the changes from trunk on 2.2.9 in my environment. Nice!
Backported to 2.2.10
*** Bug 44882 has been marked as a duplicate of this bug. ***
Undo spam change