hadoop-yarn-issues mailing list archives

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

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

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

+1 to what Jason said. Reusing the configs introduced in YARN-2001 sounds the right way to
me too. 

> 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: Robert Kanter
>         Attachments: YARN-2604.patch, YARN-2604.patch, YARN-2604.patch
>
>
> 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