Re: Haproxy config for sticky route

Hi Ruben, You are defining only one server, in your backend so even if your resolvers return 3 addresses, HAProxy will pick only one (probably the first). You need to define three servers, you can do it manually (three server lines) or use the "server-template" keyword. On 13/10/2017 14:59,

Re: Haproxy config for sticky route

Well =fun should be a variable name. But the name, whatever it is, should always be routed to the same ip based on some consistency algorhithm. I've build some DNS server to correct for the randomizing of the server list from the dns. So the following: dig @ordered-dns-proxy chat always gives

Re: Haproxy config for sticky route

On Tue, Oct 10, 2017 at 11:25 PM, Ruben wrote: > I have some stateful chat servers (SockJS) running in docker swarm mode. > When doing dig chat I get an unordered randomized list of servers for > example: > > (every time the order is different) > 10.0.0.12 > 10.0.0.10 >

Haproxy config for sticky route

I have some stateful chat servers (SockJS) running in docker swarm mode. When doing dig chat I get an unordered randomized list of servers for example: (every time the order is different) 10.0.0.12 10.0.0.10 10.0.0.11 The chat is accessed by a chatName url parameter. Now I want to be able to run