have a problem with HA / LB system, using heartbeat for HA and ldirector / ipvs for load balancing.
When the primary node is shut down or heartbeat is stopped, the migration of services works fine, but the loadbalancing does not work (ipvs rules are active, but connect connect to HA services). Configs on primary and secondary are the same:
haresources:
primary 172.16.5.1/16/bond0 ldirectord::ldirectord.cf
ldirectord.cf:
virtual = 172.16.5.1:3306
service = mysql
real = 172.16.10.1:3306 gate 1000
checktype, login, passwd, database, request values all set
scheduler = sed
ip_forward is enabled (checked via /proc, configured via sysctl)
network configs are almost the same except for the IP address (using a bonded interface in active/passive mode)
have set iptables policies to ACCEPT with rules that would not block the traffic (99.99% sure on this).
if i try connect from a server such as 172.16.10.10, i cannot connect if the secondary is up:
[user@someserver]$ mysql -h 172.16.5.1
ERROR 2003 (HY000): Can't connect to MySQL server on '172.16.5.1' (111)
perror shows that 111 is Connection Refused
running a sniffer on the secondary HA box, i dont see the tcp 3306 packets coming in.
the arp_ignore / arp_announce kernel params are configured on teh real server, HA ip address is added on a /32 subnet to the lo interface, etc, etc.... (everything works 100% when primary is up).
sure it is something i have overlooked, any idea's?
-- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
