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 2014/09/25 18:21:34 UTC

[jira] [Assigned] (YARN-56) Handle container requests that request more resources than currently available in the cluster

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

Karthik Kambatla reassigned YARN-56:
------------------------------------

    Assignee: Karthik Kambatla

> Handle container requests that request more resources than currently available in the cluster
> ---------------------------------------------------------------------------------------------
>
>                 Key: YARN-56
>                 URL: https://issues.apache.org/jira/browse/YARN-56
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: resourcemanager
>    Affects Versions: 2.0.2-alpha, 0.23.3
>            Reporter: Hitesh Shah
>            Assignee: Karthik Kambatla
>
> In heterogenous clusters, a simple check at the scheduler to check if the allocation request is within the max allocatable range is not enough. 
> If there are large nodes in the cluster which are not available, there may be situations where some allocation requests will never be fulfilled. Need an approach to decide when to invalidate such requests. For application submissions, there will need to be a feedback loop for applications that could not be launched. For running AMs, AllocationResponse may need to augmented with information for invalidated/cancelled container requests.



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