[ClusterLabs] Behavior of corosync kill

Andrei Borzenkov arvidjaar at gmail.com
Tue Aug 25 04:28:49 EDT 2020

On Tue, Aug 25, 2020 at 10:00 AM Rohit Saini
<rohitsaini111.forum at gmail.com> wrote:
> Hi All,
> I am seeing the following behavior. Can someone clarify if this is intended behavior. If yes, then why so? Please let me know if logs are needed for better clarity.
> 1. Without Stonith:
> Continuous corosync kill on master causes switchover and makes another node as master. But as soon as this corosync recovers, it becomes master again. Shouldn't it become slave now?

It is rather unclear what you are asking. Nodes cannot be master or
slave. Do you mean specific master/slave resource in pacemaker

> 2. With Stonith:
> Sometimes, on corosync kill, that node gets shooted by stonith but sometimes not. Not able to understand this fluctuating behavior. Does it have to do anything with faster recovery of corosync, which stonith fails to detect?

This could be, but logs in both cases may give more hints.

> I am using
> corosync-2.4.5-4.el7.x86_64
> pacemaker-1.1.19-8.el7.x86_64
> centos 7.6.1810
> Thanks,
> Rohit
> _______________________________________________
> Manage your subscription:
> https://lists.clusterlabs.org/mailman/listinfo/users
> ClusterLabs home: https://www.clusterlabs.org/

More information about the Users mailing list