[
https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195884#comment-15195884
]
Naganarasimha G R commented on YARN-4821:
-----------------------------------------
??is it we capture instantaneous CPU usage or CPU for the period
NMTimelinePublisher publishing?? => I mean like suppose
*resource-monitor.interval-ms* is 3 seconds and cpu metrics ATS publishing
interval is 6 seconds then we just take what ever reported by
*ContainerMonitorInterval* after 6 seconds or we store the intermediate values
average it and then push it ?
And also how to deal if *resource-monitor.interval-ms* is 3 seconds and ATS
metrics publish interval is 4/5 seconds ?
> have a separate NM timeline publishing interval
> -----------------------------------------------
>
> Key: YARN-4821
> URL: https://issues.apache.org/jira/browse/YARN-4821
> Project: Hadoop YARN
> Issue Type: Sub-task
> Components: timelineserver
> Affects Versions: YARN-2928
> Reporter: Sangjin Lee
> Labels: yarn-2928-1st-milestone
>
> Currently the interval with which NM publishes container CPU and memory
> metrics is tied to {{yarn.nodemanager.resource-monitor.interval-ms}} whose
> default is 3 seconds. This is too aggressive.
> There should be a separate configuration that controls how often
> {{NMTimelinePublisher}} publishes container metrics.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
