Re: State sync

2011-03-16 Thread Jaime Nebrera
Hi Malcom, stick-table type ip size 20k peers mypeers This part of the statement means : replicate this session table to ALL mypeers (3 other haproxy instances). Ups sorry, I didnt understand it that way. Very clear then :D Thanks -- Jaime Nebrera - jnebr...@eneotecnologia.com Consult

Re: State sync

2011-03-16 Thread Malcolm Turnbull
On 16 March 2011 10:45, Jaime Nebrera wrote: > >  Hi Malcom, > >> Source IP has a new replication feature, example here: >> >> peers mypeers >>         peer haproxy1 192.168.0.1:1024 >>         peer haproxy2 192.168.0.2:1024 >>         peer haproxy3 10.2.0.1:1024 >> >> backend mybackend >>        

Re: State sync

2011-03-16 Thread Jaime Nebrera
Hi Malcom, Source IP has a new replication feature, example here: peers mypeers peer haproxy1 192.168.0.1:1024 peer haproxy2 192.168.0.2:1024 peer haproxy3 10.2.0.1:1024 backend mybackend mode tcp balance roundrobin stick-table type ip si

Re: State sync

2011-03-15 Thread Malcolm Turnbull
Jamie, Cookies dont need state replication. Source IP has a new replication feature, example here: peers mypeers peer haproxy1 192.168.0.1:1024 peer haproxy2 192.168.0.2:1024 peer haproxy3 10.2.0.1:1024 backend mybackend mode tcp balance roundrobin

Re: State sync

2011-03-15 Thread Romeo Theriault
On Tue, Mar 15, 2011 at 23:45, Jaime Nebrera wrote: > >  Hi all list members, > >  I'm wondering if its possible to share the connection affinity / state > between a > couple of HA proxies, in such a way, in case of failure the backup server will > redirect the user to the same end server as it w

State sync

2011-03-15 Thread Jaime Nebrera
Hi all list members, I'm wondering if its possible to share the connection affinity / state between a couple of HA proxies, in such a way, in case of failure the backup server will redirect the user to the same end server as it was using when going through the main haproxy. I'm aware t