<div dir="ltr">Apologies but I'm not following. I'm probably misunderstanding something.<div><br></div><div>From what I could gather from <a href="https://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_mandatory_placement.html">https://clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/_mandatory_placement.html</a> I can't follow the subtle difference between the two on a running cluster. As an example: If backupVIP is already in node A and postgresMS:Master in node B, and postgresMS:Master dies, in my case, postgresMS:Master never gets promoted in node C. But from the -inf rule it should be able to?</div><div><br></div><div>Any insights into this would be greatly appreciated.</div></div><br><div class="gmail_quote"><div dir="ltr">On Fri, 27 Oct 2017 at 06:41 Ferenc Wágner <<a href="mailto:wferi@niif.hu">wferi@niif.hu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Norberto Lopes <<a href="mailto:nlopes.ml@gmail.com" target="_blank">nlopes.ml@gmail.com</a>> writes:<br>
<br>
> colocation backup-vip-not-with-master -inf: backupVIP postgresMS:Master<br>
> colocation backup-vip-not-with-master inf: backupVIP postgresMS:Slave<br>
><br>
> Basically what's occurring in my cluster is that the first rule stops the<br>
> Sync node from being promoted if the Master ever dies. The second doesn't<br>
> but I can't quite follow why.<br>
<br>
Getting a score of -inf means that the resource won't run. On the other<br>
hand, (+)inf just means "strongest" preference.<br>
--<br>
Regards,<br>
Feri<br>
</blockquote></div>