Bug 1695390 - GF_LOG_OCCASSIONALLY API doesn't log at first instance
Summary: GF_LOG_OCCASSIONALLY API doesn't log at first instance
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: logging
Version: 6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On: 1694925 1695391
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 02:37 UTC by Atin Mukherjee
Modified: 2019-06-25 13:24 UTC (History)
2 users (show)

Fixed In Version: glusterfs-7.0
Clone Of: 1694925
Environment:
Last Closed: 2019-06-25 13:24:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Atin Mukherjee 2019-04-03 02:37:15 UTC 
+++ This bug was initially created as a clone of Bug #1694925 +++

Description of problem:

    GF_LOG_OCCASSIONALLY doesn't log on the first instance rather at every
    42nd iterations which isn't effective as in some cases we might not have
    the code flow hitting the same log for as many as 42 times and we'd end
    up suppressing the log.


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

Mainline

How reproducible:

Always

--- Additional comment from Worker Ant on 2019-04-02 05:35:15 UTC ---

REVIEW: https://review.gluster.org/22475 (logging: Fix GF_LOG_OCCASSIONALLY API) posted (#1) for review on master by Atin Mukherjee

--- Additional comment from Worker Ant on 2019-04-02 10:57:31 UTC ---

REVIEW: https://review.gluster.org/22475 (logging: Fix GF_LOG_OCCASSIONALLY API) merged (#2) on master by Atin Mukherjee
Comment 1 Worker Ant 2019-04-03 02:39:23 UTC 
REVIEW: https://review.gluster.org/22482 (logging: Fix GF_LOG_OCCASSIONALLY API) posted (#1) for review on release-6 by Atin Mukherjee
Comment 2 Worker Ant 2019-04-03 04:54:35 UTC 
REVISION POSTED: https://review.gluster.org/22482 (logging: Fix GF_LOG_OCCASSIONALLY API) posted (#2) for review on release-6 by Raghavendra G
Note You need to log in before you can comment on or make changes to this bug.