<div dir="ltr"><div><div><div>Hello Jan,<br><br></div>Thanks for the explanation, but i saw this in my log.<br><br>::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br>
<br>corosync [TOTEM ] Process pause detected for 577 ms, flushing membership messages.<br>corosync [TOTEM ] Process pause detected for 538 ms, flushing membership messages.<br>corosync [TOTEM ] A processor failed, forming new configuration.<br>
corosync [CLM ] CLM CONFIGURATION CHANGE<br>corosync [CLM ] New Configuration:<br>corosync [CLM ] r(0) ip(10.xxx.xxx.xxx)<br>corosync [CLM ] Members Left:<br>corosync [CLM ] r(0) ip(10.xxx.xxx.xxx)<br>
corosync [CLM ] Members Joined:<br>corosync [pcmk ] notice: pcmk_peer_update: Transitional membership event on ring 6904: memb=1, new=0, lost=1<br>corosync [pcmk ] info: pcmk_peer_update: memb: node01 891257354<br>corosync [pcmk ] info: pcmk_peer_update: lost: node02 874480<br>
<br>:::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br><br></div>when this happen, corosync needs to retransmit the toten?<br>from what i understood the toten need to be retransmit, but in my case a new configuration was formed<br>
<br></div><div>This my corosync version<br><br>corosync-1.3.3-0.3.1<br><br></div><div>Thanks<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-04-30 9:42 GMT+02:00 Jan Friesse <span dir="ltr"><<a href="mailto:jfriesse@redhat.com" target="_blank">jfriesse@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Emmanuel,<br>
there is no need to trigger fencing on "Process pause detected...".<br>
<br>
Also fencing is not triggered if membership didn't changed. So let's say<br>
token was lost but during gather state all nodes replied, then there is<br>
no change of membership and no need to fence.<br>
<br>
I believe your situation was:<br>
- one node is little overloaded<br>
- token lost<br>
- overload over<br>
- gather state<br>
- every node is alive<br>
-> no fencing<br>
<br>
Regards,<br>
Honza<br>
<br>
emmanuel segura napsal(a):<br>
<div class="HOEnZb"><div class="h5">> Hello Jan,<br>
><br>
> Forget the last mail:<br>
><br>
> Hello Jan,<br>
><br>
> I found this problem in two hp blade system and the strange thing is the<br>
> fencing was not triggered :(, but it's enabled<br>
><br>
><br>
> 2014-04-25 18:36 GMT+02:00 emmanuel segura <<a href="mailto:emi2fast@gmail.com">emi2fast@gmail.com</a>>:<br>
><br>
>> Hello Jan,<br>
>><br>
>> I found this problem in two hp blade system and the strange thing is the<br>
>> fencing was triggered :(<br>
>><br>
>><br>
>> 2014-04-25 9:27 GMT+02:00 Jan Friesse <<a href="mailto:jfriesse@redhat.com">jfriesse@redhat.com</a>>:<br>
>><br>
>> Emanuel,<br>
>>><br>
>>> emmanuel segura napsal(a):<br>
>>><br>
>>> Hello List,<br>
>>>><br>
>>>> I have this two lines in my cluster logs, somebody can help to know what<br>
>>>> this means.<br>
>>>><br>
>>>> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br>
>>>> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br>
>>>> ::::::::::::::<br>
>>>><br>
>>>> corosync [TOTEM ] Process pause detected for 577 ms, flushing membership<br>
>>>> messages.<br>
>>>> corosync [TOTEM ] Process pause detected for 538 ms, flushing membership<br>
>>>> messages.<br>
>>>><br>
>>><br>
>>> Corosync internally checks gap between member join messages. If such gap<br>
>>> is > token/2, it means, that corosync was not scheduled to run by kernel<br>
>>> for too long, and it should discard membership messages.<br>
>>><br>
>>> Original intend was to detect paused process. If pause is detected, it's<br>
>>> better to discard old membership messages and initiate new query then<br>
>>> sending outdated view.<br>
>>><br>
>>> So there are various reasons why this is triggered, but today it's<br>
>>> usually VM with overloaded host machine.<br>
>>><br>
>>><br>
>>><br>
>>> corosync [TOTEM ] A processor failed, forming new configuration.<br>
>>>><br>
>>>> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br>
>>>> ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::<br>
>>>> ::::::::::::::<br>
>>>><br>
>>>> I know the "corosync [TOTEM ] A processor failed, forming new<br>
>>>> configuration" message is when the toten package is definitely lost.<br>
>>>><br>
>>>> Thanks<br>
>>>><br>
>>>><br>
>>> Regards,<br>
>>> Honza<br>
>>><br>
>>><br>
>>>><br>
>>>> _______________________________________________<br>
>>>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>>>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</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><br>
>>>><br>
>>>><br>
>>><br>
>>> _______________________________________________<br>
>>> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
>>> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</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><br>
>>><br>
>><br>
>><br>
>><br>
>> --<br>
>> esta es mi vida e me la vivo hasta que dios quiera<br>
>><br>
><br>
><br>
><br>
><br>
><br>
> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</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><br>
><br>
<br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</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><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>esta es mi vida e me la vivo hasta que dios quiera
</div>