[
https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15195891#comment-15195891
]
Sangjin Lee commented on YARN-4821:
-----------------------------------
Please feel free to assign it to yourself. I'm fine with it.
This proposal is simply to use a different publishing interval just for the
timeline publishing. We should not consider changing the nature of the CPU
usage metric (or memory) as part of this. They are still basically gauges
(instant reading of the values).
For the NM timeline publishing interval, I don't think we need to have a
super-strict publishing interval ("it must be exactly N seconds between
publishing"). I think it is perfectly fine if it is "publishing should not be
more often than every N seconds". The main purpose is to control the volume (or
speed) or writes.
> 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)
