Hello,
On Tue, Apr 08, Rafaela wrote:
> Tks Lukas!
>
> The threads of the list, it is not possible to climb HAproxy horizontally,
> how to maintain availability is using the vrrp (master and slave) or dns
> round robin (despite losing a part of traffic if you do not have to check).
> Correct?
> My traffic is great/high and working with virtual machines, only one
> haproxy working in isolation will not support all the traffic. Any other
> suggestions?
What about using keepalived to share multiple ip addresses between
multiple machines (and using dns round robin between these addresses).
Something like this in keepalived.conf:
vrrp_instance VI_1 {
...
state BACKUP
priority 100
virtual_ipaddress {
ip.addr.1
}
track_script { chk_haproxy }
}
vrrp_instance VI_2 {
...
state BACKUP
priority 99
virtual_ipaddress {
ip.addr.2
}
track_script { chk_haproxy }
...
}
vrrp_instance VI_3 {
...
state BACKUP
priority 98
virtual_ipaddress {
ip.addr.3
}
track_script { chk_haproxy }
...
}
and if you change the priorities on different servers then
VI_1 goes to server1, VI_2 to server2 and so forth. If a
server fails then one of the remaining servers will get the failed
ip address.
You'd need to have enough haproxy/keepalived servers that if some fail
then the remaining ones can handle the load.
(And dns roundrobin probably won't balance traffic "perfectly" between
the haproxy/keepalived servers).
-Jarno
>
> 2014-04-08 17:33 GMT-03:00 Lukas Tribus <[email protected]>:
>
> > Hi,
> >
> >
> > > How can I have high availability and load balancing in my HA PROXY?
> > > Using keepalived only guarantees me an online machine and is not load
> > > balancing between nodes HAproxy.
> >
> > Haproxy load balances traffic and guarantess high availability for your
> > backends. Haproxy cannot load balance its own incoming traffic if thats
> > what you are referring to.
> >
> > Is your question how to balance load on two haproxy instances?
> >
> > Take a look at the this thread:
> > http://thread.gmane.org/gmane.comp.web.haproxy/14320
