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.
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 ?
(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?
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.
Upstream patch: https://review.gluster.org/c/glusterfs/+/21262
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