Description of problem: A recent change implements per-client RPC throttling in gluster-NFS and bricks. See http://review.gluster.org/#/c/6114/. The change introduces tunable parameters that specify the threshold at which throttling is applied. In this context, it would be useful to have stats from glusterfs for: 1. number of rpc requests received by the server 2. number of throttling events 3. number of end-throttling events Such stats would help in picking good defaults for the outstanding-rpc-limit tunable parameters, in troubleshooting and in providing tuning guidelines. It would be desirable to implement this enhancement in such a way that it is easy to extend to add other stats. If we identify other events, information about which can provide similar benefits for troubleshooting and tuning, we should be able to add these to the stats collection framework.
Migrated to github issue: https://github.com/gluster/glusterfs/issues/551 Please follow the github issue for further updates on this bug.