Bug 1024695 - [RFE] Provide RPC throttling stats
[RFE] Provide RPC throttling stats
Status: NEW
Product: GlusterFS
Classification: Community
Component: core (Show other bugs)
mainline
All All
medium Severity medium
: ---
: ---
Assigned To: bugs@gluster.org
: FutureFeature, Triaged
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2013-10-30 05:34 EDT by Manoj Pillai
Modified: 2016-01-11 03:48 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Manoj Pillai 2013-10-30 05:34:56 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.