+++ This bug was initially created as a clone of Bug #1261700 +++ Description of problem: Patch to add periodic JSON dumps of FOP latency & hit rate statistics from the io-stats translator. Dumps are controlled by the diagnostics.stats-dump-interval <dump interval sec> option and stored in /var/lib/glusterd/stats under their respective FUSE, gNFSd or brick instance. This is immensely useful to reliably ferret out diagnostics & performance metrics from GlusterFS for injection into a robust analytics backend for future analysis or alarming. Heavily in-use here at Facebook. Patches clean onto the release-3.6 or release-3.7 branches as of this bug creation. Version-Release number of selected component (if applicable): v3.6.x or v3.7.x, should be trivial to port to master. How reproducible: 100% Steps to Reproduce: N/A Actual results: Expected results: Additional info: --- Additional comment from Ben England on 2015-09-22 16:55:47 EDT --- Richard, this is an extremely good idea. I have had to parse gluster volume profile output and it is extremely hard to do. JSON would make it much easier. Also, io-stats translator can run client-side so you get client-side latency, not server-side. Would be great if /usr/sbin/gluster could initiate the profiling so we didn't have to edit a volfile. Can you provide an attachment with JSON output from the patch so that lazy folks like me can see what it looks like? thx -Ben England, Perf. Engr., Red Hat --- Additional comment from on 2015-09-22 17:25 EDT --- --- Additional comment from on 2015-09-22 17:34:08 EDT --- Added example output. Also, this is automatically engaged when either of these options is enabled: diagnostics.latency-measurement diagnostics.count-fop-hits and diagnostics.ios-dump-interval ...is set to something non-zero. We run with these enabled 24x7 on all clusters at all times, and as you have noted it's extremely powerful to be able to look at performance from all layers of the stack (FUSE client, gNFSd and bricks). And with lockless counters (also in this patch) we haven't observed any perf hit. --- Additional comment from Avra Sengupta on 2015-09-25 07:23:19 EDT --- Cloning this bug to master.
Patch at http://review.gluster.org/#/c/12209/
This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions
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-3.8.0, please open a new bug report. glusterfs-3.8.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://blog.gluster.org/2016/06/glusterfs-3-8-released/ [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user