[
https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15221831#comment-15221831
]
Naganarasimha G R commented on YARN-4821:
-----------------------------------------
Thanks [~sjlee0] for detailing your idea.
bq. More importantly, if one needs to modify the resource monitoring interval,
he/she should be aware of the implication it would have on the timeline
publishing, or it's easy to miss out that connection and make a mistake.
IMO in the other approach/example which you mentioned also requires user to
consider the relation between resource monitoring interval and the publishing
interval, as events are not published as per the publishing interval.
So in the approach which i have proposed it would be easy for user to
understand and configure as events will be published based on multiple of
resource monitoring interval. like as per your example user needs to just
configure "3" . But i agree that if he is not aware that timeline publishing is
tied with resource monitoring interval then he might miss to reconfigure if he
configures the later.
bq. We could also consider different intervals for CPU and memory, although one
could argue that the YARN resource monitoring does not do that so we probably
don't need to differentiate them. That's just my 2 cents
Yeah i agree to keep it simple we can keep the same but for example if its 10
seconds then might be cpu usage we dont get the better picture of actual
utilization.
> 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)
