You are viewing a plain text version of this content. The canonical link for it is here.

Posted to yarn-issues@hadoop.apache.org by "Karthik Kambatla (JIRA)" <ji...@apache.org> on 2015/04/29 06:11:06 UTC

[jira] [Resolved] (YARN-3485) FairScheduler headroom calculation doesn't consider maxResources for Fifo and FairShare policies

     [ https://issues.apache.org/jira/browse/YARN-3485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Karthik Kambatla resolved YARN-3485.
------------------------------------
       Resolution: Fixed
    Fix Version/s: 2.7.1
     Hadoop Flags: Reviewed

Committed to trunk, branch-2 and branch-2.7 (after running TestFSAppAttempt for sanity).

Thanks Sandy, Anubhav and Arun for the reviews. 

> 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
>             Fix For: 2.7.1
>
>         Attachments: yarn-3485-1.patch, yarn-3485-2.patch, yarn-3485-3.patch, 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)