You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Siddharth Wagle (JIRA)" <ji...@apache.org> on 2016/03/01 18:29:18 UTC
[jira] [Updated] (AMBARI-15250) Collision between HBase Master and
RS metrics
[ https://issues.apache.org/jira/browse/AMBARI-15250?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Siddharth Wagle updated AMBARI-15250:
-------------------------------------
Attachment: AMBARI-15250.patch
> Collision between HBase Master and RS metrics
> ---------------------------------------------
>
> Key: AMBARI-15250
> URL: https://issues.apache.org/jira/browse/AMBARI-15250
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.0.0
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Fix For: 2.2.2
>
> Attachments: AMBARI-15250.patch
>
>
> Found out that Ganglia added the processName in JVM metrics to make this distinction::
> org.apache.hadoop.metrics.ganglia.GangliaContext#emitRecord
> {code}
> // Setup so that the records have the proper leader names so they are
> // unambiguous at the ganglia level, and this prevents a lot of rework
> StringBuilder sb = new StringBuilder();
> sb.append(contextName);
> sb.append('.');
> if (contextName.equals("jvm") && outRec.getTag("processName") != null) {
> sb.append(outRec.getTag("processName"));
> sb.append('.');
> }
> {code}
> This is missing from our Sink which means some metrics do not have unique names and will collide. _Affects HBase only_
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)