hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vinod Kumar Vavilapalli (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (YARN-2555) Effective max-allocation-* should consider biggest node
Date Tue, 16 Sep 2014 03:27:34 GMT

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

Vinod Kumar Vavilapalli resolved YARN-2555.
-------------------------------------------
    Resolution: Duplicate
      Assignee:     (was: Wei Yan)

Duplicate of YARN-56.

YARN-394 is related.

> Effective max-allocation-* should consider biggest node
> -------------------------------------------------------
>
>                 Key: YARN-2555
>                 URL: https://issues.apache.org/jira/browse/YARN-2555
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 2.5.1
>            Reporter: Karthik Kambatla
>
> The effective max-allocation-mb should be min(admin-configured-max-allocation-mb, max-mb-on-one-node),
so we can reject container requests for resources larger than any node. Today, these requests
wait forever. 
> We should do this for all resources and update the effective value on node updates. 



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

Mime
View raw message