Re: timeout client / server clarification

Greetings,

Picking this up again, there's a little problem. The directives timeout client and timeout server should be set to the same value. Imagine an upload scenario again. Imagine that both timeout directives are set to 8s (or 30s, or 120s, it doesn't really matter). Client starts uploading and data is being sent to the server. Client timeout counter is not reached because data is being sent, as John said earlier. However, if uploading takes more than 8s (in this example), the timeout server is swiftly activated...

Any obvious way to go around this, aside from increasing the timeouts? I don't want to increase them because I don't really know how much time an upload can take. I also know that a very obvious solution would be to have all uploads go to a different domain and not pass by HAProxy. Anyone dealt with this problem already?

Thanks in advance.

Pedro.

On Jul 24, 2009, at 10:37 PM, Pedro Mata-Mouros Fonseca wrote:

> Understood, thanks!
>
> Pedro
>
> On Jul 24, 2009, at 7:52 PM, John Marrett wrote:
>
>> They are inactivity timers, so if you transmit one byte (well,
>> packet,
>> really) the counter is reset.
>>
>> -JohnF
>>
>>> -----Original Message-----
>>> From: Pedro Mata-Mouros Fonseca [mailto:pedro.matamouros#sapo.pt]
>>> Sent: July 24, 2009 12:01 PM
>>> To: haproxy#formilux.org
>>> Subject: timeout client / server clarification
>>>
>>> Greetings,
>>>
>>> The timeout client and timeout server directives left me with
>>> a small
>>> doubt: are those timeouts applied if the complete response/request
>>> doesn't arrive within them, or are they applied in case no data is
>>> sent at all? Take for example a file that takes approximately 120
>>> seconds to upload to a server. If timeout client is set to 60
>>> seconds,
>>> does HAProxy close the connection after 60 seconds?
>>>
>>> Thank you so much.
>>>
>>> Pedro.
>>>
>>>
>>
>>
>
>
>
Received on 2009/08/13 13:16