Return-Path: 
 <yarn-issues-return-29501-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org>
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 EFEF411DEB
	for <apmail-hadoop-yarn-issues-archive@minotaur.apache.org>;
 Mon, 16 Jun 2014 16:16:04 +0000 (UTC)
Received: (qmail 66118 invoked by uid 500); 16 Jun 2014 16:16:04 -0000
Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org
Received: (qmail 66079 invoked by uid 500); 16 Jun 2014 16:16:04 -0000
Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:yarn-issues-help@hadoop.apache.org>
List-Unsubscribe: <mailto:yarn-issues-unsubscribe@hadoop.apache.org>
List-Post: <mailto:yarn-issues@hadoop.apache.org>
List-Id: <yarn-issues.hadoop.apache.org>
Reply-To: yarn-issues@hadoop.apache.org
Delivered-To: mailing list yarn-issues@hadoop.apache.org
Received: (qmail 66058 invoked by uid 99); 16 Jun 2014 16:16:04 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Jun 2014 16:16:04 +0000
Date: Mon, 16 Jun 2014 16:16:04 +0000 (UTC)
From: "Jason Lowe (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12653701.1371648581827.138393.1402935364392@arcas>
In-Reply-To: <JIRA.12653701.1371648581827@arcas>
References: <JIRA.12653701.1371648581827@arcas>
Subject: [jira] [Updated] (YARN-853) maximum-am-resource-percent doesn't
 work after refreshQueues command
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-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jason Lowe updated YARN-853:
----------------------------

    Fix Version/s: 0.23.11

Thanks, Deveraj!  I committed this to branch-0.23 as well.

> maximum-am-resource-percent doesn't work after refreshQueues command
> --------------------------------------------------------------------
>
>                 Key: YARN-853
>                 URL: https://issues.apache.org/jira/browse/YARN-853
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: capacityscheduler
>    Affects Versions: 3.0.0, 2.1.0-beta, 2.0.5-alpha
>            Reporter: Devaraj K
>            Assignee: Devaraj K
>             Fix For: 2.1.0-beta, 0.23.11
>
>         Attachments: YARN-853-1.patch, YARN-853-2.patch, YARN-853-3.patch, YARN-853-4.patch, YARN-853.patch
>
>
> If we update yarn.scheduler.capacity.maximum-am-resource-percent / yarn.scheduler.capacity.<queue-path>.maximum-am-resource-percent configuration and then do the refreshNodes, it uses the new config value to calculate Max Active Applications and Max Active Application Per User. If we add new node after issuing  'rmadmin -refreshQueues' command, it uses the old maximum-am-resource-percent config value to calculate Max Active Applications and Max Active Application Per User. 



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