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

Sandy Ryza commented on YARN-2422:
----------------------------------

I think it's weird to have a nodemanager property impact what goes on in the 
ResourceManager. Using this property would be especially weird on heterogeneous 
clusters where resources vary from node to node.  Preferable would be to, 
independently of yarn.scheduler.maximum-allocation-mb, make the ResourceManager 
reject any requests that are larger than the largest node in the cluster.  And 
then default yarn.scheduler.maximum-allocaiton-mb to infinite. 

> yarn.scheduler.maximum-allocation-mb should not be hard-coded in 
> yarn-default.xml
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-2422
>                 URL: https://issues.apache.org/jira/browse/YARN-2422
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 2.6.0
>            Reporter: Gopal V
>            Priority: Minor
>         Attachments: YARN-2422.1.patch
>
>
> Cluster with 40Gb NM refuses to run containers >8Gb.
> It was finally tracked down to yarn-default.xml hard-coding it to 8Gb.
> In case of lack of a better override, it should default to - 
> ${yarn.nodemanager.resource.memory-mb} instead of a hard-coded 8Gb.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to