[Pacemaker] New action for resource running in multiple nodes

Andreas Mock andreas.mock at web.de
Mon Aug 12 12:57:10 EDT 2013

Hi Adrián,


IMHO the effort would focus on the wrong issue.

Make your network for clustering reliable. It is THE building block

of a cluster besides the nodes.

- Additional network cards

- Different vendor

- Bonding

- Different path through switches


On a two-node-cluster without the necessary option to

increase the number of nodes I almost always take a crosscable

for one of the interconnects.


Best regards

Andreas Mock


P.S. The story sounds to me that you also don't have stonith

enabled. Another building block IMHO.



Von: Adrián López Tejedor [mailto:adrianlzt at gmail.com] 
Gesendet: Montag, 12. August 2013 16:26
An: pacemaker at oss.clusterlabs.org
Betreff: [Pacemaker] New action for resource running in multiple nodes




In the environment we use corosync/pacemaker, recently we are having some
problems with the network used to maintain the cluster. This short
interruptions cause the passive node (we have a two node active-passive
configuration with apache tomcat) to think he is alone, and start another
instance of tomcat. 

Few seconds later, the cluster reconnects, and the resource is found active
in both nodes. The default behaviour (as seen in
source-options.html) is to stop both, and start one of them.


For us, this implies that service is down everytime a short interruption in
the network occurs.


Maybe a new option for "multiple-active" like "stop_old" and/or "stop_new"
could be useful, stopping only the newest instance of the resource.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130812/6779019a/attachment-0003.html>

More information about the Pacemaker mailing list