Hello,
On Mon, Jun 29, 2009 at 04:44:13PM +0200, Carlo Granisso wrote:
> Ok, it seems that problem was in:
>
> contimeout
> clitimeout
>
> I've reduced these parameters and now seems that all is working fine.
> I've read haproxy documentation but I can't completly understand the meaning
> of "Set the maximum inactivity time on the client side": this mean that
> after complete download of the page haproxy leave opened the connection
> until...:
>
>
> 1) Client do some operations
> 2) Timeout reached
>
>
> Probably my problem was the second point: page was correctly loaded and
> haproxy wait for other activity.
>
> Is it correct?
I think it is even simpler than that. You have "maxconn 300" on your servers, and you don't have "option httpclose", which means that clients can maintain a keep-alive connection open an unused after they retrieve an object. By reducing "timeout client", you are forcing those connections to die faster, but it's still not the right way to do this. Please simply add "option httpclose" and I'm sure the problem will definitely vanish.
Regards,
Willy
Received on 2009/06/29 21:28
This archive was generated by hypermail 2.2.0 : 2009/06/29 21:30 CEST