Bug 1024695 - [RFE] Provide RPC throttling stats
Summary: [RFE] Provide RPC throttling stats
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-30 09:34 UTC by Manoj Pillai
Modified: 2018-11-19 04:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-19 04:56:39 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 551 0 None None None 2018-11-19 04:56:38 UTC

Description Manoj Pillai 2013-10-30 09:34:56 UTC
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.

Comment 2 Vijay Bellur 2018-11-19 04:56:39 UTC
Migrated to github issue:

https://github.com/gluster/glusterfs/issues/551

Please follow the github issue for further updates on this bug.


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