I use option 1. In your sysctl.conf, add: #Pound stuff binds even if we aren't primary net.ipv4.ip_nonlocal_bind=1
Activate it immediately with sysctl -w net.ipv4.ip_nonlocal_bind=1 Once the option is set, pound can bind to the appropriate HA-ips even if they aren't on a local interface. Which means both pound instances have an identical configuration, and there's no need to use poundctl to manipulate it in a failover event. Then use pacemaker/corosync to maintain the HA-ip on the appropriate server. If you have session affinity you'll want to use BackendCookies (or backend session replication), or a failover event will cause session restarts. Joe > -----Original Message----- > From: [email protected] [mailto:[email protected]] > Sent: Thursday, April 19, 2012 9:14 AM > To: [email protected] > Subject: [Pound Mailing List] pound with heartbeat/pacemaker > > Hi, > > I´m planing to implement a ha-loadbalancer solution depending on pound > with a heartbeat/pacemaker cluster. I think there a two possible ways > to achive this: > > 1. let pound running all the time on both nodes and switch only the HA- > IP´s between the two member. > 2.let pacemaker start and stop the pound-process and of course let > pacemaker handle the HA-IP´s. > > Question about part 1: Can pound handle added IP´s after the process > was started ? > Question about part 2: Is there an agent available or is there any > other solution to start the process via pacemaker ? > > Any suggestions or further information is welcome > > Kind regards > > fatcharly > > -- > Empfehlen Sie GMX DSL Ihren Freunden und Bekannten und wir belohnen Sie > mit bis zu 50,- Euro! https://freundschaftswerbung.gmx.de > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. N�����r��zǧu�ޙ���+a���y�n�˛���m�h���u�l��!>W���(�֜��,z��+ ��+�笶*'
