18.02.2014 14:12, Asgaroth пишет:
The 3rd node should (and needs to be) fenced at this point to allow the
cluster to continue.
Is this not happening?
The fencing operation appears to complete successfully, here is the
sequence:
[1] All 3 nodes running properly
[2] On node 3 I run "echo c > /proc/sysrq-trigger" which "hangs" node3
[3] The fence_test03 resources executes a fence operation on node 3 (fires a
shutdown/startup on the vm)
[4] dlm shows kern_stop state while node 3 is being fenced
[5] node 3 reboots, and node 1 & 2 operate as normal (clvmd and gfs2 work
properly, dlm notified that fence successful (2 members in each lock group))
[6] While node 3 is booting, cman starts properly then clvmd starts but
hangs on boot
[7] While node 3 is "hung" at the clvmd stage, node 1 & 2 are unable to
perform lvm operations due to node 3 attempting to join the clvmd "group".
Dlm shows that node 3 is a member, cman sees node 3 as a cluster member,
however, pacemaker has not started as clvmd is not successfully started.
i sometimes have the same situation. sleep ~30 seconds between startup
cman and clvmd helps a lot.
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
