Return-Path: X-Original-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Delivered-To: apmail-hadoop-yarn-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 7153718FE7 for ; Tue, 2 Jun 2015 07:46:22 +0000 (UTC) Received: (qmail 56769 invoked by uid 500); 2 Jun 2015 07:46:22 -0000 Delivered-To: apmail-hadoop-yarn-dev-archive@hadoop.apache.org Received: (qmail 56698 invoked by uid 500); 2 Jun 2015 07:46:22 -0000 Mailing-List: contact yarn-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: yarn-dev@hadoop.apache.org Delivered-To: mailing list yarn-dev@hadoop.apache.org Received: (qmail 56685 invoked by uid 99); 2 Jun 2015 07:46:21 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 Jun 2015 07:46:21 +0000 Date: Tue, 2 Jun 2015 07:46:21 +0000 (UTC) From: "skrho (JIRA)" To: yarn-dev@hadoop.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (YARN-3757) The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 skrho created YARN-3757: --------------------------- Summary: The mininum memory setting(yarn.scheduler.minimum-allocation-mb) is not working in container Key: YARN-3757 URL: https://issues.apache.org/jira/browse/YARN-3757 Project: Hadoop YARN Issue Type: Bug Components: resourcemanager Affects Versions: 2.4.0 Environment: Hadoop 2.4.0 Reporter: skrho Hello there~~ I have 2 clusters First cluster is 5 node , default 1 application queue, 8G Physical memory each node Second cluster is 10 node, 2 application queuey, 230G Physical memory each node Wherever a mapreduce job is running, I want resourcemanager is to set the minimum memory 256m to container So I was changing configuration in yarn-site.xml yarn.scheduler.minimum-allocation-mb : 256 mapreduce.map.java.opts : -Xms256m mapreduce.reduce.java.opts : -Xms256m mapreduce.map.memory.mb : 256 mapreduce.reduce.memory.mb : 256 In First cluster whenever a mapreduce job is running , I can see used memory 256m in web console( http://installedIP:8088/cluster/nodes ) But In Second cluster whenever a mapreduce job is running , I can see used memory 1024m in web console( http://installedIP:8088/cluster/nodes ) I know default memory value is 1024m, so if there is not changing memory setting, the default value is working. I have been testing for two weeks, but I don't know why mimimum memory setting is not working in second cluster Why this difference is happened? Am I wrong setting configuration? or Is there bug? Thank you for reading~~ -- This message was sent by Atlassian JIRA (v6.3.4#6332)