On Mon, Jun 10, 2013 at 03:58:56PM -0700, Ramin K wrote: > I'm seeing an very odd and consistent 10 second time to negotiate a > websocket connection when using HAproxy, but only when I have more than > one server in the rotation. > > Going directly to the server from the browser, I connect immediately. > With only one server in the haproxy backend, I connect immediately in > the browser. > > When I have two servers in the backend haproxy makes connections to both > websocket backends and exactly 10 seconds after the client had > negotiated the connection to haproxy the client considers itself > connected to socket.io application. I added a stick-table based on src > thinking it might help which didn't change the behavior. > > I tested in haproxy 1.4 (whatever the latest 12.04 LTS is shipping) and > the June 1st snapshot of 1.5. Same behavior in both cases. haproxy > server is a 64bit m1.small instance on EC2. > > I suspect that there is something off if in my cobbled together config > from various blogs and serverfault answers. I can also get some proper > tcpdump later tonight too.
Stupid question, could that not be caused by one of your servers refusing the connection from haproxy, causing it to retry until it switches back to the other server ? Otherwise I see nothing suspicious in your configuration :-/ Willy
