Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1468510

Summary:	Keep all Debug level log in circular in-memory buffer
Product:	[Community] GlusterFS	Reporter:	Sonal <sarora>
Component:	logging	Assignee:	bugs <bugs>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	low
Version:	mainline	CC:	aspandey, atumball, bugs
Target Milestone:	---	Keywords:	StudentProject, Triaged
Target Release:	---
Hardware:	Unspecified
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-04 13:53:06 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:

Description Sonal 2017-07-07 09:54:41 UTC

Description of problem:
Keep debug and trace level bugs in in-memory buffer which is useful to debug customer issues faster.
(In reference to https://github.com/gluster/glusterfs/issues/172 )

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


How reproducible:
Perform fops/operations on bricks and generate logs.

Steps to Reproduce:
1.Performs operations on bricks/mount-point.
2.Generate logs : kill -SIGUSR1 <pid>
3.Check log file.

Actual results:
Info level logs

Expected results:
Debug level logs

Additional info:

Comment 1 Worker Ant 2017-07-07 13:29:34 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#1) for review on master by Sonal Arora (sarora)

Comment 2 Worker Ant 2017-07-11 12:22:16 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#2) for review on master by Sonal Arora (sarora)

Comment 3 Worker Ant 2017-07-12 07:50:13 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#3) for review on master by Sonal Arora (sarora)

Comment 4 Worker Ant 2017-07-24 11:51:28 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#4) for review on master by Sonal Arora (sarora)

Comment 5 Worker Ant 2017-07-27 09:17:25 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#5) for review on master by Sonal Arora (sarora)

Comment 6 Worker Ant 2017-08-02 11:31:58 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#6) for review on master by Sonal Arora (sarora)

Comment 7 Worker Ant 2017-08-04 13:31:10 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#7) for review on master by Sonal Arora (sarora)

Comment 8 Worker Ant 2017-08-09 06:43:34 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#8) for review on master by Ashish Pandey (aspandey)

Comment 9 Worker Ant 2017-08-10 11:02:05 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#9) for review on master by Ashish Pandey (aspandey)

Comment 10 Worker Ant 2017-08-17 06:41:39 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#10) for review on master by Sonal Arora (sarora)

Comment 11 Worker Ant 2017-09-19 08:33:02 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#11) for review on master by Ashish Pandey (aspandey)

Comment 12 Worker Ant 2017-09-19 08:53:30 UTC

REVIEW: https://review.gluster.org/17727 (libglusterfs : Keep debug level logs in in-memory circular buffer.) posted (#12) for review on master by Ashish Pandey (aspandey)

Comment 13 Yaniv Kaul 2019-06-04 12:27:48 UTC

Since it was not implemented for ~2 years, shall we close it?

Comment 14 Ashish Pandey 2019-06-04 13:53:06 UTC

Yes, We can closing it now.