This is our configuration!!
====================================================
global
log /dev/log local2 info info
log /dev/log local3 notice
daemon
user haproxy
group haproxy
maxconn 32000
maxpipes 16000
ulimit-n 112000
nbproc 1
stats socket /tmp/https.socks uid 0 level admin
tune.maxpollevents 400
spread-checks 5
defaults
log global
option http-server-close
option dontlognull
option log-health-checks
option log-separate-errors
option redispatch
option contstats
option tcp-smart-accept
option tcp-smart-connect
option splice-auto
retries 3
timeout connect 5000
timeout http-keep-alive 30000
timeout client 20000
timeout server 20000
timeout http-request 10000
timeout queue 10000
timeout tarpit 30000
backlog 16000
frontend web
bind *:80
mode http
option httplog
maxconn 20
acl site_dead nbsrv(xxx) lt 1
acl xxx hdr_beg(host) -i xxx.com
block unless xxx
use_backend xxx if xxx
default_backend xxx
capture request header Host len 25
capture request header Referer len 100
capture request header User-Agent len 100
capture response header Via len 50
backend xxx
mode http
fullconn 100
balance roundrobin
option forwardfor except 127.0.0.1
option httpchk GET /monitor.html HTTP/1.0\r\nHost:\ xxx.com
default-server inter 3000 rise 2 fall 2
server mon.dns x.x.x.x:80
-----Original Message-----
From: "Willy Tarreau"<[email protected]>
To: "[email protected]"<[email protected]>;
Cc: <[email protected]>;
Sent: 2012-10-18 (목) 16:36:16
Subject: Re: Haproxy 1.4 and 1.5 difference (http-server-close)
Hi,
On Thu, Oct 18, 2012 at 04:11:57PM +0900, [email protected] wrote:
> Hi!!
>
> I'm using haproxy 1.4 in our production environment very well!
>
>
> Recently, I've been testing haproxy 1.5(dev11, dev12)
> I've found different operation in http-server-close option between 1.4 and
> 1.5.
>
> In 1.4,
> TCP TIMEWAIT state isn't increased in server-side!!
> (haproxy send TCP RST Packet to server after complete data transfer)
>
> but
> in 1.5(identical to 1.4 configuration),
> TCP TIMEWAIT state is increased in server-side!!
> (haproxy dont't send TCP RST Packet to server after complete data transfer)
>
> Is this a bug or how can I solve this issue?
It's not expected at all, since haproxy is supposed to disable socket
lingering before closing. Could you please send your configuration in
case we find something useful there ?
Thanks,
Willy
