[Pacemaker] Split-brain on DRBD + Corosync/Pacemaker

Felipe Gutierrez felipe.o.gutierrez at gmail.com
Wed Dec 19 06:21:09 EST 2012


Hi everyone,

I have a scenario that I disconnect my primary from the network and the
secondary assume, becaming primary. After this, I connect the younger
primary, and both nodes became secondary(DRBD), or Slave on Pacemaker. It
is because DRBD on younger Primary is Standalone and Outdated. It is a
split-brain scenario.
How do I make to my Pacemaker take care of that?
I read these
http://www.drbd.org/users-guide-8.3/s-split-brain-notification-and-recovery.html,
http://www.drbd.org/users-guide-8.3/s-configure-split-brain-behavior.html#s-automatic-split-brain-recovery-configurationand
I think I cannot configure only my DRBD resource. I believe I need to
do something on my Pacemaker.
I think Stonith is not a good idea too, because I can reconnect my younger
primary machine.

Thanks in advance,
Felipe
-- 
*--
-- Felipe Oliveira Gutierrez
-- Felipe.o.Gutierrez at gmail.com
-- https://sites.google.com/site/lipe82/Home/diaadia*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121219/97bf7325/attachment-0002.html>


More information about the Pacemaker mailing list