[Pacemaker] Stonith: How to avoid deathmatch cluster partitioning

[Klaus Darilion]

On 15.05.2013 14:51, Digimer wrote:
> 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.

Sounds good, but pacemaker does not accept the parameter:

    ERROR: st-pace1: parameter delay does not exist

The syntax suggested by you assumes that "delay" is a parameter accepted 
by the stonith resource. But this is not the case. Also "grep delay 
/usr/lib/stonith/plugins/external/*" does not reveal a single stonith 
resource which accepts this parameter.

Further, it would make sense to have "delay" as Pacemaker parameter. I 
also tried
   primitive st-pace1 stonith:external/xen0 delay="15" \
         params hostlist="pace1" dom0="xentest1" \
         op start start-delay="15s" interval="0"
but this also gives syntax errors.

Any other hints?

thanks
Klaus