Hi Willy,
On Wed, May 19, 2010 at 5:16 AM, Willy Tarreau <[email protected]> wrote:
> Hi,
>
> I have a quick comment for now, before going deep through your config.
>
> On Tue, May 18, 2010 at 03:49:57PM -0700, Chih Yin wrote:
> > As for the logs, it seems that I'll need to look at the configuration for
> > HAProxy a bit more to make some adjustments first. A few months back, I
> > know I saw messages indicating the status of server (e.g. 3 active, 2
> > backup).
>
> Normally this means that a server is failing to respond to some health
> checks,
> either because it crashed or froze, or because it's overloaded.
>
>
Wow. I'm growing concerned with this. What I've noticed is that these
messages were encountered almost daily for almost a year, but disappeared
since we migrated to the blade servers. The disconcerting part is that
since we made that migration, all indications is that the virtual servers
have been less reliable than before. Yet, I haven't seen these messages at
all.
> What I see is that your "contimeout" is set to 8 seconds and you have no
> "timeout queue". In this case, the queue timeout defaults to the
> contimeout,
> which is rather short. It means that when all your servers are saturated, a
> request will go to the queue and if no server releases a connection within
> 8 seconds, the client will get a 503. At least you should add
> "timeout queue 80s" to give more chances to your new client requests to get
> served within the previous requests' timeout. While this is a very high
> timer
> it might help troubleshoot your issues.
>
>
I guess I'm a bit confused. In the configuration file, I see the following
in the defaults section:
defaults
mode http
maxconn 1024
*contimeout 8000*
clitimeout 80000
srvtimeout 80000
*timeout queue 50000*
Am I misunderstanding and looking at the wrong spot? Also, is there a
standard timeout for the queue that is reasonable, or would this be a value
that varies from website to website?
Thank you,
C.Y.
> Regards,
> Willy
>
>
