[jira] [Created] (HADOOP-14492) RpcDetailedMetrics and NameNodeMetrics use different rate metrics abstraction cause the Xavgtime confused

["Lantao Jin (JIRA)" <ji...@apache.org>]

Lantao Jin created HADOOP-14492:
-----------------------------------

             Summary: 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
            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-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org