[
https://issues.apache.org/jira/browse/HADOOP-7507?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alejandro Abdelnur updated HADOOP-7507:
---------------------------------------
Attachment: HADOOP-7507v6.patch
v6,
For 'metrics' the original fix stays, just prefixing the processName to the
'jvm' context.
For 'metrics2' rewritten (as per Todd's suggestion) to be able to specify which
tags are to be used for the prefix.
In the hadoop-metrics2.properties the property
*PROCESS_NAME.sink.ganglia.tagsForPrefix.CONTEXT_NAME* indicates which tags are
used. If not specified, no tag is used, if '*' is specified all tags are used,
individual tags can be specified separated by commas.
For example:
{code}
namenode.sink.ganglia.tagsForPrefix.jvm=*
namenode.sink.ganglia.tagsForPrefix.dfs=*
{code}
The Context and Hostname tags are never used.
Because the default is no tags, the default behavior is backwards compatible.
> 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
> Fix For: 0.23.0
>
> Attachments: HADOOP-7507-v2.patch, HADOOP-7507v1.patch,
> HADOOP-7507v3.patch, HADOOP-7507v4.patch, HADOOP-7507v5.patch,
> HADOOP-7507v6.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
