Bug 499818

Summary: More prominent documentation of cman and split brain.
Product: Red Hat Enterprise MRG Reporter: Alan Conway <aconway>
Component: Messaging_Programming_ReferenceAssignee: Alison Young <alyoung>
Status: CLOSED CURRENTRELEASE QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: medium Docs Contact:
Priority: high    
Version: betaCC: alyoung, cctrieloff, matt
Target Milestone: 1.3Keywords: Documentation
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-17 02:02:09 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alan Conway 2009-05-08 12:28:34 UTC
A customer have suggested we make the documentation of the --qpid-cman option and the discussion of handling "split-brain" issues more prominent, since many/most cluster users will need split-brain protection. The custome didn't initially understand the requirement for cman from their initial reading of the doc.

Comment 2 Jonathan Robie 2009-09-09 15:20:27 UTC
I've added the following text:

For most applications, High Availability Messaging Clusters should be used together with Red Hat Clustering Services (RHCS) to avoid the "split-brain" condition, in which a network failure splits the cluster into two sub-clusters that cannot communicate with each other. See the documentation on the --cluster-cman option for details on running using RHCS with High Availability Messaging Clusters. See the CMAN documentation for more detail on CMAN and split-brain conditions.

Comment 3 Alan Conway 2009-09-10 13:53:18 UTC
I'd make it a bit stronger and add:

Without CMAN, a cluster cannot recover from a split-brain condition. If the network problem is resolved and the sub-clusters start communicating again the results are unpredictable.

Comment 5 Alison Young 2011-03-17 02:02:09 UTC
Closed as fix already implemented