Bug 1671213 - core: move "dict is NULL" logs to DEBUG log level
Summary: core: move "dict is NULL" logs to DEBUG log level
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 1671217 1693201
TreeView+ depends on / blocked
 
Reported: 2019-01-31 05:58 UTC by Milind Changire
Modified: 2019-03-27 10:34 UTC (History)
2 users (show)

Fixed In Version: glusterfs-6.0
Clone Of:
: 1671217 1693201 (view as bug list)
Environment:
Last Closed: 2019-02-01 03:29:51 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 22128 0 None Merged core: move \"dict is NULL\" logs to DEBUG log level 2019-02-01 03:29:43 UTC

Description Milind Changire 2019-01-31 05:58:39 UTC 
Description of problem:
too many "dict is NULL" get printed if dict_ref() and dict_unref() are passed a NULL pointer
Comment 1 Worker Ant 2019-01-31 06:02:34 UTC 
REVIEW: https://review.gluster.org/22128 (core: move \"dict is NULL\" logs to DEBUG log level) posted (#1) for review on master by Milind Changire
Comment 2 Amar Tumballi 2019-01-31 10:15:48 UTC 
Can you post some logs? Ideally, if dict is NULL during a 'ref()/unref()', it is a debug hint for developer during development. Surely should be a DEBUG log in release branch.
Comment 3 Worker Ant 2019-02-01 03:29:51 UTC 
REVIEW: https://review.gluster.org/22128 (core: move \"dict is NULL\" logs to DEBUG log level) merged (#2) on master by Amar Tumballi
Comment 4 Shyamsundar 2019-03-25 16:33:11 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.