Hello Florian, thank you for your help, the ptest commands was very useful. Perhaps this could be mentioned in the Pacemaker wiki under a Troubleshooting section? I read all the docs and didn't see it mentioned anywhere (could have missed it).
I see now what happens without the rule. I have an independent location that prefers the drbd master on my first node by 100. Together with the 10 for the synctarget it becomes more than the 100 for the syncsource. I have adjusted that preference to weight 1 and now all works the way I want it. Thanks again and enjoy your weekend, Johan On Fri, 2009-09-04 at 11:18 +0200, Florian Haas wrote: > Johan, > > If you monitor the output 'ptest -LsVVVVV 2>&1 | grep -i "master > score"', you'll notice that the RA automatically sets a low master score > for a node that is SyncTarget. It updates the master score in other > clever ways, too. > > So if you have two nodes available and one is a (DRBD) SyncTarget, it > will always pick the one that is the (DRBD) SyncSource to become > (Pacemaker) Master. > > Check drbd_update_master_score() in the RA for details. > > So to achieve what you want to achieve, do: > > crm configure delete ms-drbd0-primary-never-on-synctarget > > ... and you'll be fine. > > Cheers, > Florian > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
