[
https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15230903#comment-15230903
]
Naganarasimha G R commented on YARN-4821:
-----------------------------------------
Thanks for the comments [~vinodkv],
bq. We should completely decouple these two. If the publishing-interval is
configured to be not a multiple of the monitoring-interval, the publisher could
only look at the last N values from the monitor before the last cycle.
As we discussed in the meeting, IMHO i thought its much simpler for user to
configure just the multiple of monitoring interval after which the ATS event
will be published for the resource usage. If not user needs to be made aware of
the relation between publishing-interval and monitoring interval. So it
would be something like *monitoring interval = 3 seconds, publish frequency=
5*, then after 3*5 =15 seconds, average of 5 values will be published .
May be i can come up with a WIP patch based on this and discuss whether its fine
Will go through YARN-3332 before working on the patch.
> 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)
