In response to Lon's suggestion I modified the fence_vmware code and
set the type of reset to HARD - cluster node now resets properly.
Remaining issue is that under VMWare we are still experiencing
performance issues. It's as if a node in the cluster starts 'lagging
behind' (also the system clock starts drifting) and that after some
time one of the nodes declares the other dead.|
Does anybody have any pointers towards performance issues and/or clock drifting with GFS on virtual machines?
I'm using fence_vmware which I downloaded from some CVS repository. Good to hear that that is the issue - I'll take a look at the source and see whether the VMWare API support some sort of 'hard reset'.