hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "girish vaitheeswaran (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-2886) Track individual RPC metrics.
Date Mon, 25 Feb 2008 22:37:51 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

girish vaitheeswaran updated HADOOP-2886:

    Attachment: rpc-metrics.path

Here is a brief description of the change


+    mr.incrMetric(name + "_avg_time", (int)getPreviousIntervalAverageTime());

Cast needed since we are converting a long field to an integer and the methid incrMetric does
not have a method accepting a long field.


This file deals with dynamically obtaining the rpc latency based on the name of the rpc.


This file deals with generating the hashmap for the different RPC's. 

> 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
>         Attachments: rpc-metrics.path
> 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.

View raw message