Bug 864963

Summary:	Heal-failed and Split-brain messages are not cleared after resolution of issue
Product:	[Community] GlusterFS	Reporter:	robert.vanleeuwen
Component:	replicate	Assignee:	vsomyaju
Status:	CLOSED DEFERRED	QA Contact:
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.3.0	CC:	filip.pytloun, git, gluster-bugs, khoi.mai2008, koungho, mailbox, nsathyan, pierre.francois, pkarampu, Rob.Hendelman, rwheeler, spandura, vsomyaju
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-12-14 19:40:33 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1098027
Bug Blocks:	878881

Description robert.vanleeuwen 2012-10-10 13:50:57 UTC

Description of problem:
Whenever an issue is found it shows up when execution the volume heal command, e.g. gluster volume heal <volume> info split-brain
This list is not cleared when the issue is resolved, only way to clear it is to restart glusterd on the affected node

Version-Release number of selected component (if applicable):
Tested on 3.3


Additional info:
Would make adding monitoring easier if this state is automatically cleared when all issues are resolved

Comment 1 Pierre-Francois Laquerre 2012-12-05 13:52:55 UTC

Restarting glusterd doesn't solve this for me. The list is repopulated with the old split-brain logs after a few seconds. +1 on adding a clear feature.

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

*** Bug 871987 has been marked as a duplicate of this bug. ***

Comment 3 Pranith Kumar K 2013-03-22 05:50:21 UTC

*** Bug 905203 has been marked as a duplicate of this bug. ***

Comment 4 Anand Avati 2013-06-12 20:11:42 UTC

REVIEW: http://review.gluster.org/5209 (cluster/afr: Fix info split-brain's repetitive and redundant output) posted (#1) for review on master by venkatesh somyajulu (vsomyaju)

Comment 5 Niels de Vos 2014-11-27 14:54:00 UTC

The version that this bug has been reported against, does not get any updates from the Gluster Community anymore. Please verify if this report is still valid against a current (3.4, 3.5 or 3.6) release and update the version, or close this bug.

If there has been no update before 9 December 2014, this bug will get automatocally closed.

Comment 6 robert.vanleeuwen 2014-11-27 15:01:16 UTC

I (original reporter) cannot confirm.

This issue was discovered with a test setup and we decided to use a different (now also Red Hat ;) product.