+++ 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
REVIEW: https://review.gluster.org/22483 (logging: Fix GF_LOG_OCCASSIONALLY API) posted (#1) for review on release-5 by Atin Mukherjee
REVIEW: https://review.gluster.org/22483 (logging: Fix GF_LOG_OCCASSIONALLY API) merged (#2) on release-5 by Shyamsundar Ranganathan
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-5.6, please open a new bug report. glusterfs-5.6 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-April/000123.html [2] https://www.gluster.org/pipermail/gluster-users/