[ClusterLabs] Two-node Pacemaker cluster with "fence_aws" fence agent

[Philippe M Stedman]

Hi ClusterLabs development,

I am in the process of deploying a two-node cluster on AWS and using the
fence_aws fence agent for fencing. I was reading through the following
article about common pitfalls in configuring two-node Pacemaker clusters:
https://www.thegeekdiary.com/most-common-two-node-pacemaker-cluster-issues-and-their-workarounds/


and the only concern I have is regarding the fencing device. If I read this
correctly, there is no need to configure delayed fencing if the fence
device can guarantee serialized access. My question here is does the
fence_aws agent guarantee serialized access? In the event of a loss of
communication between the two cluster nodes, can I guarantee that one host
will win the race to fence the other and I won't end up in a situation
where both hosts get fenced.

Do I need to implement delayed fencing with the fence_aws agent or not? I
appreciate any feedback.

Thanks,

Phil Stedman
Db2 High Availability Development and Support
Email: pmstedma at us.ibm.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/users/attachments/20200904/6f0853e3/attachment.htm>