hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Varun Vasudev (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-2422) yarn.scheduler.maximum-allocation-mb should not be hard-coded in yarn-default.xml
Date Thu, 21 Aug 2014 10:29:11 GMT

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

Varun Vasudev commented on YARN-2422:
-------------------------------------

I agree with [~sandyr] on deriving the value.

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

Mime
View raw message