hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-2604) Scheduler should consider max-allocation-* in conjunction with the largest node
Date Thu, 25 Sep 2014 16:20:35 GMT

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

Karthik Kambatla resolved YARN-2604.
------------------------------------
    Resolution: Duplicate

Thanks for pointing out YARN-56, Jason. Closing this as a duplicate. Let us continue the discussion
there. 

> Scheduler should consider max-allocation-* in conjunction with the largest node
> -------------------------------------------------------------------------------
>
>                 Key: YARN-2604
>                 URL: https://issues.apache.org/jira/browse/YARN-2604
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: scheduler
>    Affects Versions: 2.5.1
>            Reporter: Karthik Kambatla
>            Assignee: Karthik Kambatla
>
> If the scheduler max-allocation-* values are larger than the resources available on the
largest node in the cluster, an application requesting resources between the two values will
be accepted by the scheduler but the requests will never be satisfied. The app essentially
hangs forever. 



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

Mime
View raw message