My LinuxHAList wrote:
In this case, node1 which is kdumping executes a kdump_pre script that tells node2 that it is kdumping.Upon this notification, node2 then tries to take over the service.
Right. So you need to make a kdump notification aware fencing agent that delays fencing when it receives kdump notification but at the same time returns fenced status immediately.
Gordan -- Linux-cluster mailing list Linux-cluster@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/linux-cluster
