On 07/25/16 17:47, Yann Ylavic wrote:
On Mon, Jul 25, 2016 at 5:18 AM, dE <de.tec...@gmail.com> wrote:
Config --
[]
ProxyPass / balancer://localbalance/ failontimeout=on timeout=10
failonstatus=502
You are defining a balancer here, so the timeout= parameter relates to
the balancer (like the two others)
However for a balancer, the timeout= parameter is not a connection
timeout (like the one used with BalancerMember), but "the maximum time
to wait for a free worker/member" (e.g. when all the workers are busy
*or* in error state, the default being to not wait).
Thus, your are hitting this timeout for each connection in your test.
You probably should use something like this instead:
ProxyPass / balancer://localbalance/ failontimeout=on
failonstatus=502 forcerecovery=off
and leave the (connection) timeout setting alone in the BalancerMember
(as you did already):
BalancerMember balancer://localbalance/ http://[fc00::1:4]/
timeout=10 retry=600
Regards,
Yann.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org
Yes, as you said I did try that before --
|BalancerMember balancer://localbalance/ http://[fc00::1:4]/ timeout=10||
||ProxyPass / balancer://localbalance/ failontimeout=on|
I even tried the retry (set to 600) and forcerecovery parameter.
Have you ever tried this in the tests that I'm doing (SIGSTOP apache)?
