You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Abhishek Modi (JIRA)" <ji...@apache.org> on 2018/12/28 12:24:00 UTC
[jira] [Commented] (YARN-4821) Have a separate NM timeline
publishing-interval
[ https://issues.apache.org/jira/browse/YARN-4821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16730222#comment-16730222 ]
Abhishek Modi commented on YARN-4821:
-------------------------------------
[~Naganarasimha] if you are not actively working on it, can I take this.
> 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
> Priority: Major
> Labels: YARN-5355
> Attachments: YARN-4821-YARN-2928.v1.001.patch
>
>
> 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
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org