Inigo Goiri commented on YARN-3534:

I could first do the NodeResourceMonitorImpl and then add that info it to the 
heartbeat in a second JIRA. However, I thought the addition to the heartbeat 
was simple enough. Anyways, up to you; I can split it in two.

Regarding the extra ResourceUtilizations layers, I could get rid of them for 
now as it's not currently needed. However, in parallel, I'm privately working 
on a scheduler which is aware of utilization and it's much better to use those 
layers as I need the floats for the CPUs instead of plain int. I thought about 
making ResourceUtilizaiton an extension of Resource but it does not work...

Anyway, I'll send a patch without the extra ResourceUtilizations layer as it's 
not really required for this patch. Does that sound reasonable?

> Report node resource utilization
> --------------------------------
>                 Key: YARN-3534
>                 URL: https://issues.apache.org/jira/browse/YARN-3534
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: nodemanager, resourcemanager
>    Affects Versions: 2.7.0
>            Reporter: Inigo Goiri
>            Assignee: Inigo Goiri
>         Attachments: YARN-3534-1.patch, YARN-3534-2.patch, YARN-3534-3.patch, 
> YARN-3534-3.patch
>   Original Estimate: 336h
>  Remaining Estimate: 336h
> YARN should be aware of the resource utilization of the nodes when scheduling 
> containers. For this, this task will implement the NodeResourceMonitor and 
> send this information to the Resource Manager in the heartbeat.

This message was sent by Atlassian JIRA

Reply via email to