My LinuxHAList wrote:
What can I do at node2 to forcefully take over the service from node1 after node2 is contacted by node1 at kdump_pre stage ?
Sounds like you need to write your own fencing script that will return successfully fenced status when it knows node2 is down and dumping, and only reboot it some time later. How can you remotely check that the failed node is actually kdumping?
Gordan -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
