[
https://issues.apache.org/jira/browse/AMBARI-5607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13994004#comment-13994004
]
Dmytro Sen commented on AMBARI-5607:
------------------------------------
The main cause of the bug is hided in the default rrdtool/rrdfetch
configuration and Ganglia's gmetad.conf
If we don't set "s" parameter to rrd.py (rrdtool fetch, in fact) is uses
default option values "s=now-1day&e=now". For the specified period circular
buffer #2 contains more complete and detailed data than buffer #1. Setting
default value between 6 minutes and 1 hour.
The patch is attached to the Review Board
> Yarn Nodemanager Metrics only update every few minutes
> ------------------------------------------------------
>
> Key: AMBARI-5607
> URL: https://issues.apache.org/jira/browse/AMBARI-5607
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.5.1
> Environment: sles11sp1
> Reporter: Michael Harp
> Assignee: Dmytro Sen
>
> Yarn Nodemanager Metrics take far too long between updates.
> To demonstrate:
> Run Terasort or anything that runs mapreduce:
> {code}
> hdfs dfs -mkdir -p benchmarks/terasort
> hadoop jar /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar teragen
> -Dmapred.map.tasks=72 -Dmapred.reduce.tasks=36 1000000
> benchmarks/terasort/input
> hadoop jar /usr/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar terasort
> -Dmapred.map.tasks=72 -Dmapred.reduce.tasks=36 benchmarks/terasort/input
> benchmarks/terasort/output
> hdfs dfs -rm -R -skipTrash benchmarks/terasort
> {code}
> Then repeatedly probe the API at:
> {noformat}https://<server>:8081/api/v1/clusters/c1/services/YARN/components/NODEMANAGER?fields=host_components/metrics/yarn{noformat}
> It usually takes 2-3 minutes to see the metrics update, very repeatable.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
