[DRBD-user] Resolving split brain

David Pullman david.pullman at gmail.com
Fri Jun 3 18:38:27 CEST 2016

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

We have a two node cluster that has Pacemaker and DRBD 8.4 on RHEL 6
configured in HA. The application is a monitoring system that has a web
front end and uses Postgresql as a backend. The Postgres db uses the DRBD
device for it's datastore.

I'm trying to get a configuration that will deterministically resolve split
brain when it happens. The first priority is to have one and only one node
running the HA stack and have that updating the database with monitoring
data. The second priority is, in the event of a split brain, to resolve to
the most recent content.

I've looked at the automatic split brain recovery in the docs, and tried a
couple of things but I think I'm missing something to get the resolution in
the case of two standalones. Also, I'm thinking based on some other list
entries that fencing is the way to go, but I'm not sure how to proceed.

I'm getting split brain on occasion when the I/O between the nodes goes
down. We have two switches in a redundant configuration connecting the
nodes. For unrelated reasons I can't change the interconnect.

Any suggestions, referrals to docs, etc., would be greatly appreciated.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linbit.com/pipermail/drbd-user/attachments/20160603/925133ed/attachment.htm>

More information about the drbd-user mailing list