Return-Path: X-Original-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AEBB111190 for ; Mon, 18 Aug 2014 20:57:19 +0000 (UTC) Received: (qmail 94429 invoked by uid 500); 18 Aug 2014 20:57:19 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 94385 invoked by uid 500); 18 Aug 2014 20:57:19 -0000 Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-issues@hadoop.apache.org Delivered-To: mailing list yarn-issues@hadoop.apache.org Received: (qmail 94372 invoked by uid 99); 18 Aug 2014 20:57:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Aug 2014 20:57:19 +0000 Date: Mon, 18 Aug 2014 20:57:19 +0000 (UTC) From: "Sandy Ryza (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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)