On 15 Nov 2013, at 4:37 am, Michael Jones <[email protected]> wrote:
>>> Hello, >>> >>> I'm attempting to use pacemaker/corosync (1.1.10/2.31) in a two node >>> active/passive embedded application where all resources should run only on >>> one node. I'm looking for a configuration option that will "remember" the >>> last active node when the appliance is rebooted. I'm using postgresql >>> replication and would like the appliance to always boot to the most >>> recently active node! > >> Do you mean that after the cluster was completely stopped and starts on both >> nodes, you want the application to remember which node it was on prior to >> the cluster stopping? > > That's correct. Sorry, I should have clarified, the two nodes that I'm > talking about are in the same appliance connected by a backplane. It seems > like I need to set some attribute on a node that can be used in a rule, > maybe? We don't natively support such a feature, but you could have your resource agent create/update a location constraint to push it to one node or the other.
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
