<div dir="ltr"><div class="gmail_extra"><br><div class="gmail_quote">2015-06-08 14:23 GMT+02:00 Andrei Borzenkov <span dir="ltr"><<a href="mailto:arvidjaar@gmail.com" target="_blank">arvidjaar@gmail.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><span class="">On Mon, Jun 8, 2015 at 3:05 PM, Oscar Salvador<br>
<<a href="mailto:osalvador.vilardaga@gmail.com">osalvador.vilardaga@gmail.com</a>> wrote:<br>
> Hi guys!<br>
><br>
> I've configured two nodes with the stack pacemaker + corosync, with only one<br>
> resource ( just for test purposes ), and I'm having a strange result.<br>
><br>
> First a little bit of information:<br>
><br>
> pacemaker version: 1.1.12-1<br>
> corosync version: 2.3.4-1<br>
><br>
><br>
> # crm configure show<br>
> node 1053402612: server1 \<br>
> node 1053402613: server2<br>
> primitive IP-rsc_apache IPaddr2 \<br>
> params ip=xx.xx.xx.xy nic=eth0 cidr_netmask=255.255.255.192 \<br>
> meta migration-threshold=2 \<br>
> op monitor interval=20 timeout=60 on-fail=standby<br>
> property cib-bootstrap-options: \<br>
> last-lrm-refresh=1433763004 \<br>
> stonith-enabled=false \<br>
> no-quorum-policy=ignore<br>
><br>
</span>...<br>
<span class="">><br>
><br>
> It seems like pacemaker is assuming that the monitor-operation failed, and<br>
> because of this, decides to mark the node as a standby. But should not be,<br>
> no?<br>
><br>
<br>
</span>You told it to do exactly that (on-fail=standby).<br>
<br>
_______________________________________________<br>
Users mailing list: <a href="mailto:Users@clusterlabs.org">Users@clusterlabs.org</a><br>
<a href="http://clusterlabs.org/mailman/listinfo/users" target="_blank">http://clusterlabs.org/mailman/listinfo/users</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a></blockquote><div><br></div><div><br></div><div>Yes, I told that: if the monitor-operation failed, put the node in standby. But from my point of view, the monitor-operation doesn't fail, but the resource itself.</div><div>I'm very stranged with this because as I told, I tested this with and old version of pacemaker, and it didn't have this behaviour.</div><div>Maybe I was consufed because of that.</div><div><br></div><div>So, somehow is reduntant do something like that:<br></div></div></div><div class="gmail_extra"><br></div><div class="gmail_extra">meta migration-threshold=2<br></div><div class="gmail_extra">op monitor interval=20 timeout=60 on-fail=standby<br></div><div class="gmail_extra"><br></div><div class="gmail_extra">since it will never reach the failcount of 2, no?</div></div>