[Pacemaker] how to get pacemaker:ping recheck before promoting drbd resources on a node

[Jelle de Jong]

Hello everybody,

I need to be able to bring down my network interface (network failure
test) and few seconds later bring it up again. Without my drbd cluster
going nuts and creating split brains.

I was advised to use ocf:pacemaker:ping, so I started to integrate this
in my configuration: http://pastebin.com/raw.php?i=iyp3URkP

Now the problem is that it kind of works, but not the way I need it to be.

The ping status is not rechecked right _before_ it tries to promoted the
drbd resources. If should do a fast ping check and continue if
successful but _don’t_ promote any drbd resources when it stalls or fails.

The problem is that the ping have been returning good values back until
the network failure and when the failure accrues it is still thinking
the ping status is good and promotes the disk until and few seconds
later the ping status changes to indicate the network failure, but then
all damage is already made...

I must be doing something _terrible_ wrong since I can't believe a
pacemaker/corosync cluster shouldn't be able to survive a network glitch
(short network failures) without all kind of split brains and losing the
node.

Thanks in advance,

Kind regards,

Jelle de Jong

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 316 bytes
Desc: OpenPGP digital signature
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20110418/0ac9e16f/attachment-0002.sig>