Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: core-dev@hadoop.apache.org
Message-ID: <1070297629.1205799986985.JavaMail.jira@brutus>
Date: Mon, 17 Mar 2008 17:26:26 -0700 (PDT)
From: "Sanjay Radia (JIRA)" <jira@apache.org>
To: core-dev@hadoop.apache.org
Subject: [jira] Commented: (HADOOP-2886) Track individual RPC metrics.
In-Reply-To: <748678098.1203722119393.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12579688#action_12579688 ] 

Sanjay Radia commented on HADOOP-2886:
--------------------------------------

+1

> 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.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.