On 05/10/2013 05:55 PM, Todor Genov wrote:
> Excerpts from Heikki Vatiainen's message of Fri May 10 15:55:22 +0200 2013:
>> Since you have not specified FailureBackoffTime it defaults to 0 and
>> might be the cause of the problem you see.
>
> Even with a "FailureBackoffTime 300" the problem is re
Hi Heikki,
Excerpts from Heikki Vatiainen's message of Fri May 10 15:55:22 +0200 2013:
> Since you have not specified FailureBackoffTime it defaults to 0 and
> might be the cause of the problem you see.
Even with a "FailureBackoffTime 300" the problem is reproducible. For now I'll
revert to usin
On 05/10/2013 02:33 AM, Todor Genov wrote:
> I have found an issue where the "Retries" clause is ignored when using
> UseStatusServerForFailureDetect with "AuthBy LOADBALANCE".
Hello Todor,
We have recently received reports about Status-Server probing and there
appears to be some issues that re
P.S a worse scenario unfolds when the downstream host is responding to Auth
(and Status-Server), but not to Accounting. In this case Accounting is still
being load-balanced to the downstream host, but all requests enter an infinite
re-transmit loop until they are accepted.
With high volumes of
Hi,
I have found an issue where the "Retries" clause is ignored when using
UseStatusServerForFailureDetect with "AuthBy LOADBALANCE".
In a scenario where a downstream proxy becomes unresponsive requests enter a
re-transmit loop until the next Status-Server keepalive detects the host has
failed
