Bug 1654236

Summary:	Provide an option to silence glfsheal logs
Product:	[Community] GlusterFS	Reporter:	Ravishankar N <ravishankar>
Component:	replicate	Assignee:	Ravishankar N <ravishankar>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5	CC:	bugs
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-5.2	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1643519	Environment:
Last Closed:	2019-03-27 13:40:34 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:	1643519
Bug Blocks:	1654229

Description Ravishankar N 2018-11-28 10:14:18 UTC

+++ This bug was initially created as a clone of Bug #1643519 +++

Description of problem:

Many monitoring/reporting solutions run 'gluster volume heal $volname info' and its related subcommands very frequently (even once every minute), leading to unnecessary filling up of the glfsheal logs. (See downstream BZs 1579293 and 1631851 for instance). The main intention of running these commands is to process/consume the output displayed on stdout/xml format and not really the gluster client logs which glfsheal (which is gfapi based) generates under /var/log/glusterfs/glfsheal*.

Hence it is useful to have a --nolog option which will prevent the incessant logging. 

Note that these logs are VERY helpful when debugging when heal-info is unresponsive/hung/disconnected from bricks or when running split-brain resolution commands. So the default log level is still kept at GF_LOG_INFO and is changed to GF_LOG_NONE only when the command is invoked with the --nolog flag.

--- Additional comment from Worker Ant on 2018-10-26 08:46:03 EDT ---

REVIEW: https://review.gluster.org/21501 (glfsheal: add a '--nolog' option) posted (#1) for review on master by Ravishankar N

--- Additional comment from Worker Ant on 2018-11-26 03:36:51 EST ---

REVIEW: https://review.gluster.org/21501 (glfsheal: add a '--nolog' flag) posted (#5) for review on master by Pranith Kumar Karampuri

Comment 1 Worker Ant 2018-11-28 10:16:33 UTC

REVIEW: https://review.gluster.org/21741 (glfsheal: add a '--nolog' flag) posted (#1) for review on release-5 by Ravishankar N

Comment 2 Worker Ant 2018-11-29 15:32:03 UTC

REVIEW: https://review.gluster.org/21741 (glfsheal: add a '--nolog' flag) posted (#1) for review on release-5 by Ravishankar N

Comment 3 Shyamsundar 2019-03-27 13:40:34 UTC

This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-5.2, please open a new bug report.

glusterfs-5.2 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution.

[1] https://lists.gluster.org/pipermail/announce/2018-December/000117.html
[2] https://www.gluster.org/pipermail/gluster-users/