[Pacemaker] How to avoid CRM sending stop when ha.cf gets 2nd node configured

Andrew Beekhof andrew at beekhof.net
Sun Nov 9 22:29:15 EST 2014

> On 8 Nov 2014, at 11:58 am, aridh bose <aridbh at yahoo.com> wrote:
> Hi,
> While using heartbeat and pacemaker, is it possible to bringup first node which can go as Master, followed by second node which should go as Slave without causing any issues to the first node? Currently, I see a  couple of problems in achieving this:
> 1. Assuming I am not using mcast communication, heartbeat is mandating me to configure second node info either in ha.cf or in /etc/hosts file with associated IP address. Why can't it come up by itself as Master to start with?

Because its not using mcast and therefor doesn't know how to talk to other nodes in the future.

> 2. If I update ha.cf with the 2nd node info and use 'heartbeat -r' CRM first sends stop on the Master before sending start.
> Appreciate any help or pointers.
> Thanks,
> Aridbh.
> _______________________________________________
> 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