Hi, > Hello , > > Many thanks for your replay. This thing is more stranger i downloaded and > compiled serverl versions of HAproxy 1.5.x.x and the result was alwase the > same > > I experimented with following versions > > At first i testing with > http://haproxy.1wt.eu/download/1.5/src/devel/haproxy-1.5-dev21.tar.gz > > After i tested with these > http://haproxy.1wt.eu/download/1.5/src/devel/haproxy-1.5-dev20.tar.gz > http://haproxy.1wt.eu/download/1.5/src/devel/haproxy-1.5-dev18.tar.gz > http://haproxy.1wt.eu/download/1.5/src/devel/haproxy-1.5-dev17.tar.gz > > latest downloded was haproxy-ss-LATEST.tar.gz from > http://haproxy.1wt.eu/download/1.5/src/snapshot/ > > All the time the result was same
Well, your make line looks very specific, whats the reason you use those CFLAGS manually and don't use on the other hand a specific TARGET? I suggest you give this a try: make clean; make TARGET=linux2628 CPU=native USE_PCRE=1 USE_OPENSSL=1 \ USE_ZLIB=1 With the custom make TARGET, you are not using epoll, falling back to the slower poll(). This shouldn't make any difference regarding the ssl affinity though. Regarding that, your configuration looks ok, and you have tested a different releases, which make me think the issue may not be in haproxy. How do you know HAProxy doesn't maintains the correct affinity? Are you tcpdumping the frontent traffic? Are you sure your backend servers have an session cache enabled and working? Regards, Lukas
