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 "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/03/15 19:25:33 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=15195874#comment-15195874 ] 

Naganarasimha G R commented on YARN-4821:
-----------------------------------------

Hi [~sjlee0], 
One query wrt this is how to calculate the cpu usage as the duration could be different, is it we capture instantaneous CPU usage or CPU for the period NMTimelinePublisher publishing ? 
Also would like to work on this jira

> 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)