Thanks Amyas!
But why just connect to the Direct (transparent) connection so high. And the
connection to our web backend is normal. So I doubt is option timeout server
should change in the Direct like
backend Direct
mode tcp
timeout server 30s
log global
option tcplog
no option httpclose
no option http-server-close
no option accept-invalid-http-response
no option http-pretend-keepalive
option transparent
option abortonclose
option nolinger
Regards
Jinge
On 2013-7-11, at 下午3:26, Amyas <[email protected]> wrote:
> jinge <altman87120@...> writes:
>
>
>> timeout connect 5s
>
> Willy will say that 5s is not long enough for a lost packet
> during the connect phase.
> Maybe that should be in the docs or a warning in the
> config check mode.
>
>> Is there any turning argument for solve this problem?
>
> Some of it does not need to be solved, if you are churning many connections,
> you will always have alot of connections in various closing states.
>
> That said, I am not sure all your timeouts and settings are optimal - like
> abort
> and queue timeout same as client/server timeouts, etc.
> Others will have better suggestions on those.
>
>
