[
https://issues.apache.org/jira/browse/YARN-7680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16590235#comment-16590235
]
Zoltan Siegl edited comment on YARN-7680 at 8/23/18 2:04 PM:
-------------------------------------------------------------
Hey [~ajisakaa]!
I have been trying to fix or reproduce this on apache/trunk without any success.
In the code I have found 4 places where
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainerMetrics#forContainer(org.apache.hadoop.yarn.api.records.ContainerId,
long, long) is referenced, and all of those are invoked only if the
yarn.nodemanager.container-metrics.enable config is set to true.
Steps taken to reproduce:
* Run a pseudo distributed hadoop cluster
* {{run hadoop jar
hadoop-3.2.0-SNAPSHOT/share/hadoop/mapreduce/hadoop-mapreduce-examples-3.2.0-SNAPSHOT.jar
pi 10 10}} to fire up some containers.
If yarn.nodemanager.container-metrics.enable config is set to false I have seen
no signs of ContainerMetrics being registered whatsoever.
Additionally I have set an output file for
{{nodemanager.sink.file.filename=nodemanager-metrics.out}} and greping any sign
in there for ContainerMetrics with
{{tail -f nodemanager-metrics.out | grep -i ContainerMetrics}}
still without any luck.
Could you provide a way to reproduce this issue?
was (Author: zsiegl):
Hey [~ajisakaa]!
I have been trying to fix or reproduce this on apache/trunk without any success.
In the code I have found 4 places where
org.apache.hadoop.yarn.server.nodemanager.containermanager.monitor.ContainerMetrics#forContainer(org.apache.hadoop.yarn.api.records.ContainerId,
long, long) is referenced, and all of those are invoked only if the
yarn.nodemanager.container-metrics.enable config is set to true.
Steps taken to reproduce:
* Run a pseudo distributed hadoop cluster
* {{run hadoop jar
hadoop-3.2.0-SNAPSHOT/share/hadoop/mapreduce/hadoop-mapreduce-examples-3.2.0-SNAPSHOT.jar
pi 10 10}} to fire up some containers.
If yarn.nodemanager.container-metrics.enable config is set to false I have seen
no signs of ContainerMetrics being registered whatsoever.
Could you provide a way to reproduce this issue?
> ContainerMetrics is registered even if
> yarn.nodemanager.container-metrics.enable is set to false
> ------------------------------------------------------------------------------------------------
>
> Key: YARN-7680
> URL: https://issues.apache.org/jira/browse/YARN-7680
> Project: Hadoop YARN
> Issue Type: Bug
> Components: metrics
> Affects Versions: 3.0.0
> Reporter: Akira Ajisaka
> Assignee: Zoltan Siegl
> Priority: Critical
>
> ContainerMetrics is unintentionally registered to DefaultMetricsSystem even
> if yarn.nodemanager.container-metrics.enable is set to false. For example,
> when we set
> *.sink.ganglia.class=org.apache.hadoop.metrics2.sink.ganglia.GangliaSink31 to
> sink all the metrics to Ganglia, MetricsSystem sink ContainerMetrics to
> ganglia server (localhost:8649 by default).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
