[Pacemaker] Stonith: How to avoid deathmatch cluster partitioning
Digimer
lists at alteeve.ca
Wed May 15 12:51:14 UTC 2013
On 05/15/2013 08:37 AM, Klaus Darilion wrote:
> primitive st-pace1 stonith:external/xen0 \
> params hostlist="pace1" dom0="xentest1" \
> op start start-delay="15s" interval="0"
Try;
primitive st-pace1 stonith:external/xen0 \
params hostlist="pace1" dom0="xentest1" delay="15" \
op start start-delay="15s" interval="0"
The idea here is that, when both nodes lose contact and initiate a
fence, 'st-pace1' will get a 15 second reprieve. That is, 'st-pace2'
will wait 15 seconds before trying to fence 'st-pace1'. If st-pace1 is
still alive, it will fence 'st-pace2' without delay, so pace2 will be
dead before it's timer expires, preventing a dual-fence. However, if
pace1 really is dead, pace2 will fence it and recovery, just with a 15
second delay.
--
Digimer
Papers and Projects: https://alteeve.ca/w/
What if the cure for cancer is trapped in the mind of a person without
access to education?
More information about the Pacemaker
mailing list