hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3481) Report NM aggregated container resource utilization in heartbeat
Date Thu, 30 Apr 2015 04:13:06 GMT

    [ https://issues.apache.org/jira/browse/YARN-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14520825#comment-14520825

Vinod Kumar Vavilapalli commented on YARN-3481:

Sorry, didn't realize before. This is a dup of YARN-2965?

IAC, as I commented on YARN-2965, this is getting increasingly messy: we keep re-measuring
the same thing in multiple places - ContainersMonitorImpl (existing code), Timeline Service
Next-gen (YARN-2928), and this JIRA.

[~elgoiri], can you please look at my doc at YARN-3332?

[~vvasudev], please look at this - this is relevant to some of the efforts you are doing to
expose metrics (for e.g. YARN-3503). I think we need to lay the groundwork for unified stats
collection to avoid this repeated measurements.

> Report NM aggregated container resource utilization in heartbeat
> ----------------------------------------------------------------
>                 Key: YARN-3481
>                 URL: https://issues.apache.org/jira/browse/YARN-3481
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: nodemanager, resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Inigo Goiri
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> To allow the RM take better scheduling decisions, it should be aware of the actual utilization
of the containers. The NM would aggregate the ContainerMetrics and report it in every heartbeat.
> Related to YARN-1012 but aggregated to reduce the heartbeat overhead.

This message was sent by Atlassian JIRA

View raw message