[ClusterLabs] Pacemaker quorum behavior

Jan Pokorný jpokorny at redhat.com
Thu Sep 29 14:38:38 EDT 2016

On 28/09/16 16:30 -0400, Scott Greenlese wrote:
> Also,  I have tried simulating a failed cluster node (to trigger a
> STONITH action) by killing the corosync daemon on one node, but all
> that does is respawn the daemon ...  causing a temporary / transient
> failure condition, and no fence takes place.   Is there a way to
> kill corosync in such a way that it stays down?   Is there a best
> practice for STONITH testing?

This makes me seriously wonder what could cause this involuntary
daemon-scoped high availability...

Are you sure you are using upstream provided initscript/unit file?

(Just hope there's no fence_corosync_restart.)

Jan (Poki)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20160929/fadc24c0/attachment-0003.sig>

More information about the Users mailing list