Bug 762769 (GLUSTER-1037)

Summary:	selfheal information in normal logging mode
Product:	[Community] GlusterFS	Reporter:	Raghavendra Bhat <rabhat>
Component:	replicate	Assignee:	Pranith Kumar K <pkarampu>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	mainline	CC:	gluster-bugs, tejas, vijay, vikas
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:		Type:	---
Regression:	RTNR	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Raghavendra Bhat 2010-06-30 07:04:37 UTC

If the glusterfs is started with normal logging mode, then the logs corresponding to selfheal are not printed in the logfile. One need to run in trace mode to get the information. Changes have to be made such that self heal messages are printed (filename, type of selfheal such as data selfheal or meatadata selfheal and the cause which triggered the selfheal) in the log file when run in normal mode itself.

Comment 1 Vikas Gorur 2010-07-06 13:30:29 UTC

The downside to printing every self-heal is that it can make the log files grow very big. People routinely self-heal terabytes of data and that can easily swell the log file to hundreds of megabytes.

Comment 2 Anand Avati 2010-07-23 08:29:00 UTC

PATCH: http://patches.gluster.com/patch/3850 in master (custer/afr added self-heal logging in normal mode)

Comment 3 Anand Avati 2010-07-27 10:48:50 UTC

PATCH: http://patches.gluster.com/patch/3913 in master (cluster/afr: Logging improvement for self-heal)

Comment 4 Pranith Kumar K 2010-07-28 06:29:06 UTC

Tested the bug by reproducing the bugs 974, 950 with my fix. The self-heal logs showed up with the reason for the self-heal.
need to enhance the logs further if these are not enough.