On Tue, Feb 24, 2015 at 1:39 AM, Francois Lagier <[email protected]> wrote:
> Hello everyone, > > I am currently trying to tune my HaProxy architecture (65k queries per > seconds, low latency requirement (<50ms), with 12 servers using multi-core > (4 cores per server)) and I have a couple of questions about the > http-keep-alive timeout and the behavior when we are actually timing out. > In my situation, it looks like the client (using KAL) is not sending me the > data and it's triggering an Eof Exception on my backend once HaProxy is > timing out and that's why I would like to reset the connection with the > client. > > My question to help me understand what's happening: > > - What is the default "timeout http-keep-alive" value when it's not > specify in the configuration? > > Docs say it defaults to "timeout http-request" which itself defaults to "timeout client". So, from your gist, your timeout http-keep-alive looks to be 3 seconds. > > - > - In case of a timeout (at the server level in this case) with > keep-alive configured (option http-server-close), is the session going to > stay active or is going to get closed after returning the 5xx? What will be > the best way for me to close it after a timeout? > > In my experience the tcp connection is closed when the response is a 500. I'm not sure if that's documented though. > > - > > Here is my current configuration for timeouts and options: > https://gist.github.com/francoislagier/3f666253ba61f7b0784c > > Thank you very much and have a great day. > > Best, > Francois > > > >
