ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Siddharth Wagle (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-15293) Capture HDFS metrics per RPC port number in AMS and Grafana
Date Fri, 04 Mar 2016 01:26:40 GMT

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

Siddharth Wagle commented on AMBARI-15293:
------------------------------------------

----------------------------------------------------------------------
Ran 244 tests in 7.160s

OK
----------------------------------------------------------------------
Total run:893
Total errors:0
Total failures:0
OK

> Capture HDFS metrics per RPC port number in AMS and Grafana
> -----------------------------------------------------------
>
>                 Key: AMBARI-15293
>                 URL: https://issues.apache.org/jira/browse/AMBARI-15293
>             Project: Ambari
>          Issue Type: Improvement
>          Components: ambari-metrics
>    Affects Versions: 2.0.0
>            Reporter: Siddharth Wagle
>            Assignee: Siddharth Wagle
>            Priority: Critical
>             Fix For: 2.2.2
>
>         Attachments: AMBARI-15293.patch
>
>
> For rpc metrics the port number determines what rpc calls are being tracked. 
> _Example_: Namenode can have different rpc ports for Datanode and clients and healthchecks.
Presently since the port number is not a part of the metricsName the two metric entries will
step on each other in AMS store.
> This patch only addresses the fix for HDFS.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message