You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2016/03/09 22:05:40 UTC
[jira] [Updated] (AMBARI-15293) Capture HDFS metrics per RPC port
number in AMS and Grafana
[ https://issues.apache.org/jira/browse/AMBARI-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-15293:
-------------------------------------
Attachment: AMBARI-15293-2.patch
Missing check for metrics with already suffixed aggregate functions
+ Missing nameserice id in the port calculation.
Both issues found during manual testing and verified to be fixed with the patch.
> 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-2.patch, 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)