[Pacemaker] reg. clone/master-slave

Andrew Beekhof andrew at beekhof.net
Tue Jun 11 20:48:42 EDT 2013


On 06/06/2013, at 4:03 PM, ESWAR RAO <eswar7028 at gmail.com> wrote:

> Hi All,
> 
> Can someone please help me in below scenario:
> 
> I want my daemon running on 2 nodes to be monitored using HB+pacemaker.
> The daemon is already running before the RA is configured using crm,
> 
> #crm configure primitive my_daemon lsb::testd meta allow-migrate="true" is-managed="false" migration-threshold="1" failure-timeout="30s" op monitor interval="5s" on-fail="standby"

why is-managed="false"?

> 
> #crm configure clone my_daemon_clone my_daemon
> 
> I configured it using clone.
> 
> From pacemaker guide I saw:
> 
> Clones: for services which need to be active on multiple nodes
> Multi-state: for services with multiple modes (eg. master/slave, primary/seco ndary)
> 
> I just want to know when the RA need to configured as clone and when they need to be configured as master-agent.

If they all do the same thing: use a clone

> 
> 
> Thanks
> Eswar
> 
> 
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
> 
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org





More information about the Pacemaker mailing list