hadoop-yarn-issues mailing list archives

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

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

Robert Kanter updated YARN-2604:
--------------------------------
    Attachment: YARN-2604.patch

The new patch addresses Karthik's 2nd suggestion.  That actually made it so that we didn't
need to exclude anything from findbugs, making the 1st suggestion moot now.

I spoke to Karthik offline; the 3rd suggestion does not apply because we're not looking for
the node to remove it; we're looking for the new largest node.

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