Hi Rob,
On Wed, Dec 05, 2007 at 10:34:30AM -0500, Rob wrote:
> Hello all, hope everyone is doing fine.....
>
> If i do not give any or do not have the srv & clitimeout options in the
> config, does haproxy default to anything, or there is simply no time
> outs at all?
You will get an infinite timeout with a warning at startup.
> As a setting of 750000 still gives errors to dialup clients that have
> large emails for sending or receiving...
Hmmm. I have an idea on the subject, I must check the code. Since haproxy intially was only HTTP-oriented, communications were mostly half-duplex with known states where the client was not expected to talk while retrieving data for instance. However, in TCP mode, communications are often full-duplex (eg: SSH or remote displays), so data which passes in each direction freshens the expiration timers. But it is fairly normal to expect the client to be able to talk after retrieving 30 minutes of data, so both the read and write timeouts should be updated when it speaks. I have to check the code because I must admit I'm not sure what is done in this specific case.
In the mean time, you'd have to increase your timeouts even higher. I know people who put 3 hours timeouts on some production servers, at least it's better than infinite.
Regards,
Willy
Received on 2007/12/05 23:21
This archive was generated by hypermail 2.2.0 : 2007/12/05 23:30 CET