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

Wed Dec 19 11:41:49 UTC 2012

cutting the communication link between the two nodes is not a valid
failover scenario. both side will think that other nodes offline and become
primary. and if you reconnect them, the splitbrain will happen. you can
make the communication link redundant between the two nodes. maybe these
articles can help :
http://www.hastexo.com/blogs/martin/2012/07/11/failover-testing-some-technical-background
http://www.drbd.org/users-guide-8.3/s-prepare-network.html

On Wed, Dec 19, 2012 at 6:21 PM, Felipe Gutierrez <
felipe.o.gutierrez at gmail.com> wrote:

> 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*
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20121219/9625002d/attachment.htm>