Inigo Goiri commented on YARN-3534:

The original reason for having ResourceUtilization was getting better 
granularity for the CPUs. We had some discussion about it in YARN-3481; take a 
look there and chim in.

My original implementation had Resource but when trying to do scheduling of 
containers based on this, there were a lot of holes in the scheduling. Given 
this, I thought this patch was a good place to create this new utilization 
entity with CPU as a float.

Regarding the metrics in the NodeResourceMonitor, I completely agree. I thought 
about doing it right away but as you mentioned, it seemed a better idea to save 
it for another JIRA. Let's do that.

> 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