[
https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15207633#comment-15207633
]
Naganarasimha G R commented on YARN-4821:
-----------------------------------------
[~sjlee0], I was thinking more in the lines : for how many container resource
monitors we publish the container usage value for example for every 2nd monitor
publish the usage metrics so if monitoring interval is 3 seconds then we
publish metrics every 6 seconds. In this way it would be better, as publishing
interval cannot be independent as it depends on container resource monitoring
period.
And also other thing to note here i can understand this approach(having more
publish interval) for Memory but CPU would it make sense to collect after gaps
like n intervals say for example 2 intervals of 3 seconds gap, then we would be
collecting for every 6 seconds but usually cpu usage is not constant for such a
long time right ? Would it be required to handle differently for CPU and Memory
?
> 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
> Assignee: Naganarasimha G R
> 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)
