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

Karthik Kambatla commented on YARN-2604:
----------------------------------------

bq. I guess it comes down to whether we really want to immediately fail an app 
if no node in the cluster at the time of submission has the sufficient 
resources. If that's OK then we can do a simple change like the one you 
originally proposed.
This would be light-weight and quick particularly for mis-configuration cases, 
and I think there is merit to doing this in addition to YARN-56. Let me re-open 
this and work on a patch. 

> 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)

Reply via email to