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

Inigo Goiri commented on YARN-3481:
-----------------------------------

[~vinodkc] thanks for fixing the JIRA; these are my first tries and I'm not 
aware of what is the best practice.

Regarding the approach to send information, I agree that creating a new type 
(ResourceUtilization is the proposal) might be the best way to go. I started 
implementing it this way and it's basically a copy of Resource for now with a 
float for the VCores. I'll try to keep both up to sync but it might be 
challenging. Is there anything we can do to keep them coupled? What about 
ResourceUtilizaiton extending Resource? It doesn't look clean to me so I hope 
there might be a better way.

> 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
(v6.3.4#6332)

Reply via email to