<html><body><p><font size="2">Hi ClusterLabs development,<br><br>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:<br></font><a href="https://www.thegeekdiary.com/most-common-two-node-pacemaker-cluster-issues-and-their-workarounds/"><font size="2">https://www.thegeekdiary.com/most-common-two-node-pacemaker-cluster-issues-and-their-workarounds/</font></a><font size="2"><br><br>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.</font><font size="2"> 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.<br><br>Do I need to implement delayed fencing with the fence_aws agent or not? I appreciate any feedback.<br><br>Thanks,</font><br><br><b><font size="2">Phil Stedman</font></b><br><font size="2">Db2 High Availability Development and Support<br>Email: pmstedma@us.ibm.com</font><BR>
</body></html>