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

Luke Lu commented on HADOOP-7507:
---------------------------------

This is actually not the right fix as jvm metrics already set the processName 
tag. The right place to fix this is actually in ganglia plugin to encode tags 
as part of the metrics names, as the problem not only happens to jvm metrics 
but also other per tag metrics as well, say per queue metrics in capacity 
scheduler.

Both metrics1 and metrics2 Ganglia{Plugin,Sink} needs to be fixed. Metrics2 is 
what hadoop will be using for trunk/0.23. Some downstream projects like HBase 
will still use metrics1 for compatibility reasons (working with multiple hadoop 
releases from 0.20 to 0.23 etc.)

> jvm metrics all use the same namespace
> --------------------------------------
>
>                 Key: HADOOP-7507
>                 URL: https://issues.apache.org/jira/browse/HADOOP-7507
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: metrics
>    Affects Versions: 0.20.2
>            Reporter: Jeff Bean
>            Assignee: Alejandro Abdelnur
>         Attachments: HADOOP-7507v1.patch, JvmMetrics.java, 
> hadoop-metrics.properties, screenshot-1.jpg
>
>
> Ganglia jvm metrics don't make sense because it's not clear which java 
> process the metrics refer to. In fact, all hadoop java processes running on a 
> node report their jvm metrics to the same namespace.
> The metrics are exposed by the "jvm" context in JvmMetrics.java. This leads 
> to confusing and nonsensical graphs in ganglia and maybe other monitoring 
> tools.
> One way to fix this is to make sure the process name is reported in the jvm 
> context, making it clear which process is associated with the context, and 
> separating out the jvm metrics per process.
> This is marked as an "incompatible change" because the fix provided removes 
> the JVM metrics and replaces it with process-specific metrics.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to