Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 7 Jun 2017 14:38:18 +0000 (UTC)
From: "Lantao Jin (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.13077533.1496716056000.18785.1496846298408@Atlassian.JIRA>
In-Reply-To: <JIRA.13077533.1496716056000@Atlassian.JIRA>
References: <JIRA.13077533.1496716056000@Atlassian.JIRA> <JIRA.13077533.1496716056514@jira-lw-us.apache.org>
Subject: [jira] [Commented] (HADOOP-14492) RpcDetailedMetrics and
 NameNodeMetrics use different rate metrics abstraction cause the Xavgtime
 confused
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 07 Jun 2017 14:38:25 -0000


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

Lantao Jin commented on HADOOP-14492:
-------------------------------------

Thanks [~xkrogen] to explain. Yes, our DataNode run with multiple storages. Assigning to you is good. I think it better to use a different metrics name like {{WholeDNBlockReportAvgTime}}.

> RpcDetailedMetrics and NameNodeMetrics use different rate metrics abstraction cause the Xavgtime confused
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-14492
>                 URL: https://issues.apache.org/jira/browse/HADOOP-14492
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 2.8.0, 2.7.4
>            Reporter: Lantao Jin
>            Assignee: Erik Krogen
>            Priority: Minor
>
> For performance purpose, [HADOOP-13782|https://issues.apache.org/jira/browse/HADOOP-13782] change the metrics behaviour in {{RpcDetailedMetrics}}.
> In 2.7.4:
> {code}
> public class RpcDetailedMetrics {
>   @Metric MutableRatesWithAggregation rates;
> {code}
> In old version:
> {code}
> public class RpcDetailedMetrics {
>   @Metric MutableRates rates;
> {code}
> But {{NameNodeMetrics}} still use {{MutableRate}} whatever in the new or old version:
> {code}
> public class NameNodeMetrics {
>   @Metric("Block report") MutableRate blockReport;
> {code}
> It causes the metrics in JMX very different between them.
> {quote}
> name: "Hadoop:service=NameNode,name=RpcDetailedActivityForPort8030",
> modelerType: "RpcDetailedActivityForPort8030",
> tag.port: "8030",
> tag.Context: "rpcdetailed",
> ...
> BlockReportNumOps: 237634,
> BlockReportAvgTime: 1382,
> ...
> name: "Hadoop:service=NameNode,name=NameNodeActivity",
> modelerType: "NameNodeActivity",
> tag.ProcessName: "NameNode",
> ...
> BlockReportNumOps: 2592932,
> BlockReportAvgTime: 19.258064516129032,
> ...
> {quote}
> In the old version. They are correct.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org