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

Karthik Kambatla commented on YARN-3485:
----------------------------------------

[~peng.zhang] - I am not sure I understand your latest comments. 

FairScheduler's Fifo and Fair policies don't consider CPU max resources when 
calculating headroom. However, these policies consider CPU at allocation time. 
So, the potential maximum allocation for an app ends up being smaller than the 
headroom. If apps wait for headroom amount of resources, they will never get 
them. This JIRA attempts to fix that issue. 

> FairScheduler headroom calculation doesn't consider maxResources for Fifo and 
> FairShare policies
> ------------------------------------------------------------------------------------------------
>
>                 Key: YARN-3485
>                 URL: https://issues.apache.org/jira/browse/YARN-3485
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: fairscheduler
>    Affects Versions: 2.7.0
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>            Priority: Critical
>         Attachments: yarn-3485-prelim.patch
>
>
> FairScheduler's headroom calculations consider the fairshare and 
> cluster-available-resources, and the fairshare has maxResources. However, for 
> Fifo and Fairshare policies, the fairshare is used only for memory and not 
> cpu. So, the scheduler ends up showing a higher headroom than is actually 
> available. This could lead to applications waiting for resources far longer 
> than then intend to. e.g. MAPREDUCE-6302.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to