Comment 19 for bug 1436343

There is another split case reproduced while testing this:

When there is a minority partition w/o a quorum:

node-3: Mon Apr 13 09:05:38 UTC 2015
Current DC: node-3.test.domain.local (3) - partition with quorum
Online: [ node-2.test.domain.local node-3.test.domain.local ]
OFFLINE: [ node-1.test.domain.local ]

node-2: Mon Apr 13 09:05:38 UTC 2015
Current DC: node-2.test.domain.local (2) - partition WITHOUT quorum
Online: [ node-2.test.domain.local ]
OFFLINE: [ node-1.test.domain.local node-3.test.domain.local ]

Tthis case clearly shows that no-quorum-policy=stop works excellent and prevents split brain. But the node in minority partition should still be "healed" manually or STONITHed in order to return back in the cluster. Note, that later this minority partition gains quorum, which is *very* strange, but resources still kept stopped, so it is acceptable:

  Current DC: node-2.test.domain.local (2) - partition with quorum
  Online: [ node-2.test.domain.local ]
  OFFLINE: [ node-1.test.domain.local node-3.test.domain.local ]