Bug 1666833 - move few recurring logs to DEBUG level.
Summary: move few recurring logs to DEBUG level.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Amar Tumballi
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-16 17:04 UTC by Amar Tumballi
Modified: 2019-03-25 16:33 UTC (History)
1 user (show)

Fixed In Version: glusterfs-6.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-03-25 16:33:07 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22053 0 None Open core: move logs which are only developer relevant to DEBUG level 2019-01-23 16:06:21 UTC

Description Amar Tumballi 2019-01-16 17:04:53 UTC
Description of problem:
Reduce the log chatter due to some repeated logs in master branch.

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

How reproducible:
100%

Additional Info:

These were already fixed in release branches, https://review.gluster.org/#/c/glusterfs/+/21173/ but kept as is, so we can fix each of these.

But considering these logs are causing extra headache in understanding the proper issue, while debugging, it makes sense to move these to DEBUG log-level.

Comment 1 Worker Ant 2019-01-16 17:09:10 UTC
REVIEW: https://review.gluster.org/22053 (core: move logs which are only developer relevant to DEBUG level) posted (#2) for review on master by Amar Tumballi

Comment 2 Worker Ant 2019-01-23 16:06:22 UTC
REVIEW: https://review.gluster.org/22053 (core: move logs which are only developer relevant to DEBUG level) merged (#3) on master by Shyamsundar Ranganathan

Comment 3 Shyamsundar 2019-03-25 16:33:07 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-6.0, please open a new bug report.

glusterfs-6.0 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/2019-March/000120.html
[2] https://www.gluster.org/pipermail/gluster-users/


Note You need to log in before you can comment on or make changes to this bug.