[
https://issues.apache.org/jira/browse/AMBARI-15293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15188272#comment-15188272
]
Hudson commented on AMBARI-15293:
---------------------------------
SUCCESS: Integrated in Ambari-trunk-Commit #4473 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/4473/])
AMBARI-15293. Capture HDFS metrics per RPC port number in AMS and (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=cbc3f1a900367d27ed69748cbec31e1b73bb28be])
*
ambari-server/src/main/resources/stacks/HDP/2.0.6/hooks/before-START/scripts/params.py
*
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
> 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)
