Bug 871987 - Split-brain logging is confusing
Summary: Split-brain logging is confusing
Keywords:
Status: CLOSED DUPLICATE of bug 864963
Alias: None
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: All
medium
low
Target Milestone: ---
Assignee: vsomyaju
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 878881
TreeView+ depends on / blocked
 
Reported: 2012-10-31 22:36 UTC by Dynamic Packet
Modified: 2015-03-05 00:06 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
: 878881 (view as bug list)
Environment:
Last Closed: 2013-02-22 09:48:26 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)

Description Dynamic Packet 2012-10-31 22:36:41 UTC
Description of problem:

 Currently, split-brain logs are not cleared after resolution. This may (and does) confuse users who manually heal/fix split-brain'ed files but still see them in this log. Its equally confusing that if you miss files in this process and heal again, the split-brain list grows. 

How reproducible:

 Every time

Steps to Reproduce:
1. Create volume with replica 2
2. Cause split-brain on 1 file
3. Manually fix split-brain
4. Log entry still appears
  
Expected results:

 It would be great if the split-brain list was cleared when starting another heal. Or if the files could be removed from the list once the split-brain state was fixed manually.

Comment 1 Pranith Kumar K 2012-11-02 07:25:39 UTC
hi,
  Could you explain what you mean by log. The one that is written to the file or the entry that appears in 'volume heal <volname> info split-brain'? Could you also let us know the version of gluster you are using.

Pranith

Comment 2 Joe Julian 2012-11-02 14:11:35 UTC
This is referring to the 'volume heal <volname> info split-brain' output on any of the release-3.3 versions.

Comment 3 Pranith Kumar K 2013-02-22 09:48:26 UTC

*** This bug has been marked as a duplicate of bug 864963 ***


Note You need to log in before you can comment on or make changes to this bug.