Bug 1631166

Summary:	Provide indication at the console or in the logs about the progress being made with changelog processing.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Yaniv Kaul <ykaul>
Component:	glusterfind	Assignee:	Milind Changire <mchangir>
Status:	CLOSED ERRATA	QA Contact:	Vinayak Papnoi <vpapnoi>
Severity:	high	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	mchangir, rhs-bugs, sanandpa, sankarshan, sheggodu, storage-qa-internal
Target Milestone:	---	Keywords:	Improvement, UserExperience, ZStream
Target Release:	RHGS 3.4.z Batch Update 2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	glusterfs-3.12.2-27	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:
Clones:	1632236 (view as bug list)		Environment:
Last Closed:	2018-12-17 17:07:04 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:	1632236
Bug Blocks:

Description Yaniv Kaul 2018-09-20 07:00:10 UTC

Description of problem:
From https://bugzilla.redhat.com/show_bug.cgi?id=1599802#c105 :
Currently there's no indication at the console or in the logs about the progress being made with changelog processing.

glusterfind could add a log entry per changelog file to the log file, but we risk on accumulating large log files if the number of changelogs are huge ... like in this case.

Or, glusterfind could log a "completed parsing CHANGELOG.xxxxxxxxx" entry, per changlog file to the stderr. I think logging to stderr is better.

Comment 1 Milind Changire 2018-09-20 08:47:39 UTC

I was mistaken. glusterfind does log progress to the log file as a series of following logs:

[2018-09-20 08:43:00.704936] D [MSGID: 0] [gf-history-changelog.c:78:gf_history_changelog_done] 0-gfchangelog: moving /usr/local/var/lib/misc/glusterfsd/glusterfind/test1/patchy/20180920-044255-673115-M0j4S2/1553b38fb1ffed164736f80f40d3c46a99a84ff4/.history/.processing/CHANGELOG.1537421769 to processed directory

Is there anything else that is desired ?

Comment 2 Yaniv Kaul 2018-09-20 09:06:45 UTC

(In reply to Milind Changire from comment #1)
> I was mistaken. glusterfind does log progress to the log file as a series of
> following logs:
> 
> [2018-09-20 08:43:00.704936] D [MSGID: 0]
> [gf-history-changelog.c:78:gf_history_changelog_done] 0-gfchangelog: moving
> /usr/local/var/lib/misc/glusterfsd/glusterfind/test1/patchy/20180920-044255-
> 673115-M0j4S2/1553b38fb1ffed164736f80f40d3c46a99a84ff4/.history/.processing/
> CHANGELOG.1537421769 to processed directory
> 
> Is there anything else that is desired ?

Rate I assume is what is being asked usually. Why did you need strace if you have the above log?

Comment 3 Milind Changire 2018-09-20 09:12:00 UTC

We had a suspicion that the 'gfid to path' conversion is not optimal. The 'gfid to path' conversion happens after all the changelogs are processed. Also, there's no indication in the logs that the 'gfid to path' conversion has commenced. So the inclination to request the strace.

Comment 4 Milind Changire 2018-10-04 07:21:49 UTC

Upstream patch: https://review.gluster.org/c/glusterfs/+/21262

Comment 11 errata-xmlrpc 2018-12-17 17:07:04 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2018:3827