[
https://issues.apache.org/jira/browse/HADOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
dhruba borthakur updated HADOOP-2886:
-------------------------------------
Status: Open (was: Patch Available)
There seems to be one findbugs warning that was caught by the HadoopQA tests.
It would be nice if you can fix them and resubmit the patch.
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1994/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
> Track individual RPC metrics.
> -----------------------------
>
> Key: HADOOP-2886
> URL: https://issues.apache.org/jira/browse/HADOOP-2886
> Project: Hadoop Core
> Issue Type: Improvement
> Components: metrics
> Reporter: girish vaitheeswaran
> Fix For: 0.17.0
>
> Attachments: rpc-metrics.patch, rpc-metrics.patch, rpc-metrics.path,
> rpcmetrics.patch, rpcmetrics.patch
>
>
> There is currently no mechanism to track performance metrics at the
> granularity of a specific RPC. So For e.g. if we wanted to capture average
> latency for the openFile RPC or for the createFile RPC the current
> infrastructure does not support that.
> The implementation involves having a simple HashMap where every new Rpc
> metric being added would be inserted into the HashMap. Since there is a
> mechanism to obtain RPC latencies already (without the name of the specific
> RPC), the identification of what RPC is involved would be done by doing a
> lookup on the HashMap.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
