[Pacemaker] Reboot node with stonith after killing a corosync-process?

Andrew Beekhof andrew at beekhof.net
Fri Apr 15 07:20:28 EDT 2011

On Fri, Apr 15, 2011 at 12:09 PM, Dominik Klein <dk at in-telegence.net> wrote:
> Hi
> On 04/15/2011 09:05 AM, Tom Tux wrote:
>> I can reproduce this behavior:
>> - On node02, which had no resources online, I killed all corosync
>> processes with "killall -9 corosync".
>> - Node02 was rebootet through stonith
>> - On node01, I can see the following lines in the message-log (line 6
>> schedules the STONITH):
>> For me it seems, that node01 recognized, that the cluster-processes on
>> node02 were not shot down properly. So the behavior in this case is,
>> to stonith the node. Could this behavior be disabled? Which setting?
> The cluster cannot distinguish between a node that has lost power, has
> broken network or someone killed corosync there.
> To the surviving node, the other one is just dead and stonith makes sure
> it really is.
> That's expected and i guess it will not change.

100% correct

More information about the Pacemaker mailing list