Helllo Jan,
I'm using corosync+pacemaker on Sles 11 Sp1 and this is a critical system,
i don't think i'll get the authorization for upgrade system, but i would
like to know if there is any bug about this issue in my current corosync
release.
Thanks
Emmanuel
2014-04-30 17:07 GMT+02:00 Jan Friess
Emmanuel,
emmanuel segura napsal(a):
> Hello Jan,
>
> Thanks for the explanation, but i saw this in my log.
>
> ::
>
> corosync [TOTEM ] Process pause detected for 577
Hello Jan,
Thanks for the explanation, but i saw this in my log.
::
corosync [TOTEM ] Process pause detected for 577 ms, flushing membership
messages.
corosync [TOTEM ]
Anonymous:184136 kB
AnonHugePages: 0 kB
Swap: 103112 kB
KernelPageSize:4 kB
MMUPageSize: 4 kB
Locked:0 kB
VmFlags: rd wr mr mw me ac
20140430
7f92e1578000-7f92fc01d000 rw-p 00:00 0 [heap]
Size: 436
Size: 4 kB
Locked:0 kB
VmFlags: rd wr mr mw me ac
20140430
7f92e1578000-7f92fc01d000 rw-p 00:00 0 [heap]
Size: 436884 kB
Rss: 140812 kB
Pss: 140812 kB
Shared_Clean: 0 kB
Shared_
Emmanuel,
there is no need to trigger fencing on "Process pause detected...".
Also fencing is not triggered if membership didn't changed. So let's say
token was lost but during gather state all nodes replied, then there is
no change of membership and no need to fence.
I believe your situation was
