Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Tue, 16 Sep 2014 03:30:34 +0000 (UTC)
From: "Vinod Kumar Vavilapalli (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12734530.1408140718000.41253.1410838234213@Atlassian.JIRA>
In-Reply-To: <JIRA.12734530.1408140718000@Atlassian.JIRA>
References: <JIRA.12734530.1408140718000@Atlassian.JIRA>
 <JIRA.12734530.1408140718985@arcas>
Subject: [jira] [Commented] (YARN-2422) yarn.scheduler.maximum-allocation-mb
 should not be hard-coded in yarn-default.xml
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Vinod Kumar Vavilapalli commented on YARN-2422:
-----------------------------------------------

It's not just weird, but it's broken on heterogeneous clusters. The right fix is a dup of YARN-56.

> 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
>            Assignee: 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.3.4#6332)