io-stats bugs and features
REVIEW: https://review.gluster.org/19007 (debug/io-stats: Adding stat for weighted & unweighted average latency) posted (#1) for review on master by
REVIEW: https://review.gluster.org/19009 (debug/io-stats: Track path of operations in FOP samples) posted (#1) for review on master by Shreyas Siravara
REVIEW: https://review.gluster.org/19016 (debug/io-stats: Add errors to FOP samples) posted (#1) for review on master by
COMMIT: https://review.gluster.org/19007 committed in master by with a commit message- debug/io-stats: Adding stat for weighted & unweighted average latency Summary: - Our current approach to measuring "average fop latency" is badly flawed in that it doesn't weight the FOPs correctly according to how many occurred in the time interval. This makes Statisticians very sad. This patch adds an internally computed weighted average latency which will be far more efficient to display via ODS, as well as having the benefit of not being complete nonsense. Reviewers: kvigor, dph, sshreyas Reviewed By: sshreyas Change-Id: Ie3618f279b545610b7ed1a8482243fcc8dc53217 BUG: 1523353 Reviewed-on: https://review.gluster.org/18192 Reviewed-by: Shreyas Siravara <sshreyas> Smoke: Gluster Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.org> Signed-off-by: Ana M. Neri <amnerip>
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-4.0.0, please open a new bug report. glusterfs-4.0.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] http://lists.gluster.org/pipermail/announce/2018-March/000092.html [2] https://www.gluster.org/pipermail/gluster-users/