Re: State sync

   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 size 20k peers mypeers
> stick on src
>
> server srv1 192.168.30:80
> server srv2 192.168.31:80

   Sorry for my ignorance, but were is the replication of state between two different haproxy servers, one acting as active the other as passive?

   I mean, seems this is internal to a single server, you are stating, maintain flow affinity based on source ip. Great, but how does the other balancer know about this decission?

> BTW: LVS can easily do session replication just use:
> ipvsadm --start-daemon master
> ipvsadm --start-daemon backup

   Yep, I'm aware this can be done with lvs, my doubt is if it can be done with haproxy too.

   Regards

-- 
Jaime Nebrera - jnebrera#eneotecnologia.com
Consultor TI - ENEO Tecnologia SL
C/ Manufactura 2, Edificio Euro, Oficina 3N
Mairena del Aljarafe - 41927 - Sevilla
Telf.- 955 60 11 60 / 619 04 55 18