On 7/18/2015 3:50 AM, mlist wrote:
Ok. Thank you. I read and tested little more haproxy. As now I use haproxy to
balance web applications (http/https).
As I can test, for web application load balancing "cookie insert" on all
haproxy configuration can handle failover as client connect always with cookie inserted
by ne of load balancer. So at failover the new contacted load balancer know where to
route request and session works well.
Probably also Sticky table works, but with cookie insert there is more
independence between LBs. I read about clients problems with more cookie set,
is this a real problem or a problem only for old browsers (agents) ?
I ask you a last question: do you have experience with LVS L4 load balancer in
front of Hhaproxy ?
How you resolved VIP arp problem ? As I know the simple solution is to add VIP
on lo interface, using arp_announce and arp_ignore. I'm using a CentOS 7 with
kernel 3.10.0-229.7.2.el7
Can you point me in the right direction ?
My haproxy installs uses pacemaker to handle failover. I have resources
in pacemaker for the VIP, haproxy, and gratuitous arp for the VIP, so
that other hosts on the LAN will instantly know that the IP address has
moved.
Pacemaker has constraints so that the arp and haproxy must be on the
same host as the vip, and so the vip starts before everything else.
Here is my full pacemaker config with the public IP address redacted:
http://apaste.info/OU4
Thanks,
Shawn
