[
https://issues.apache.org/jira/browse/HADOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12580320#action_12580320
]
Hadoop QA commented on HADOOP-2886:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12377815/rpcmetrics.patch
against trunk revision 619744.
@author +1. The patch does not contain any @author tags.
tests included -1. The patch doesn't appear to include any new or modified
tests.
Please justify why no tests are needed for this patch.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new javac compiler
warnings.
release audit +1. The applied patch does not generate any new release
audit warnings.
findbugs -1. The patch appears to introduce 1 new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1994/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1994/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1994/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/1994/console
This message is automatically generated.
> 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.
