Re: Haproxy failover: DNS RR vs Virtual IP (heartbeat, keepalived)

On 6-1-2011 10:51, Brett Delle Grazie wrote:
> The best solution would depend upon your requirements but an optimal one
> (with no requirement for a server to be dormant until failure - i.e.
> pure HA) is (for 2 node load balancer):
> 2 IPs registered in DNS-RR
> 2 virtual IPs which are those listed in DNS-RR.
> HAproxy running on both nodes
> Cluster controlling software (RHCS or Corosync + Pacemaker or Heartbeat
> + Pacemaker) managing virtual IPs and HA proxy on both nodes. According
> to current advice from linux-cluster and pacemaker mailing lists - stay
> away from Heartbeat 2.x - I know this is supplied by most distributions
> but it is buggy and doesn't handle certain corner cases well.
>
> Hope this helps.

And if you want to have your pacemaker+corosync cluster up within the next hour, follow this howto on my site ;)

http://blog.hongens.nl/guides/setting-up-a-pacemaker-cluster-on-centosrhel/

-- 


With kind regards,


Angelo Höngens
systems administrator

MCSE on Windows 2003
MCSE on Windows 2000
MS Small Business Specialist
------------------------------------------
NetMatch
tourism internet software solutions

Ringbaan Oost 2b
5013 CA Tilburg
+31 (0)13 5811088
+31 (0)13 5821239

A.Hongens#netmatch.nl
www.netmatch.nl
------------------------------------------