We have the same use case as Alex *(mesos load balancing), and also confirm
that our config worked without change 1.6->1.8.
Given our testing you should consider the seamless reload -x option, and
the dynamic server configuration apis. Both have greatly alleviated issues
we've faced in our
I can speak from a production point of view that we had HAproxy on the 1.6
branch inside docker containers for mesos load balancing with pretty much
the same requirements as you spoke of. After compiling Haproxy to the 1.8x
branch the same config worked without issues.
On Mon, Jul
We have been running the 1.6 branch of HAProxy, without any issues, for a
while now. And reading the updates around 1.8 here in the mailing list it
looks like its time to upgrade to this branch.
So I was wondering if there are any things I need to look of for when doing
Mail list logo