Thanks. Looks like it is websocket connections for us too. So is killing the process the only way?
Thanks, Wei On 1/27/14, 11:47 PM, "k simon" <[email protected]> wrote: > We got the simlar problem, then capture the traffic and found it's >result in websocket. So we had to kill the old process manually when >finished graceful restart. > > > >于 28/1/14 下午2:37, Willy Tarreau 写道: >> On Mon, Jan 27, 2014 at 11:24:46PM +0000, Wei Kong wrote: >>> We use >>> >>> /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -D -p >>>/var/run/haproxy.pid -sf <pid> >>> >>> In production to gracefully restart haproxy. But sometimes we notice >>>that the >>> old haproxy process taking a long time to go away and if we make >>>multiple >>> updates and it would result in multiple haproxy processes for a long >>>time. >>> How can we make sure the old haproxy can go away in a reasonable >>>amount of >>> time? >> >> Maybe you have long transfers going on, or long keep-alive timeouts ? >> >> Willy >> >>
