Mailing-List: contact yarn-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: yarn-issues@hadoop.apache.org
Date: Thu, 7 May 2015 09:36:00 +0000 (UTC)
From: "zhoulinlin (JIRA)" <jira@apache.org>
To: yarn-issues@hadoop.apache.org
Message-ID: <JIRA.12827972.1430991313000.34300.1430991360316@Atlassian.JIRA>
In-Reply-To: <JIRA.12827972.1430991313000@Atlassian.JIRA>
References: <JIRA.12827972.1430991313000@Atlassian.JIRA>
 <JIRA.12827972.1430991313691@arcas>
Subject: [jira] [Created] (YARN-3590) Change the attribute "maxRunningApps"
  of FairSchudeler queue,it should be take effect for application in
 queue,but not
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

zhoulinlin created YARN-3590:
--------------------------------

             Summary: Change the attribute "maxRunningApps"  of FairSchudeler queue,it should be take effect for application in queue,but not
                 Key: YARN-3590
                 URL: https://issues.apache.org/jira/browse/YARN-3590
             Project: Hadoop YARN
          Issue Type: Bug
          Components: fairscheduler
    Affects Versions: 2.5.2
            Reporter: zhoulinlin


Change the queue attribute "maxRunningApps"  for  FairSchuduler, and then refresh queues, it should effect the application in queue immediately,but not.
To take effect, the condition is that another application move from this queue. 

For example:the "maxRunningApps" is 0, summbit a application A to this queue, it can't be run. Then change "maxRunningApps" from 0 to 2 and refresh quque, application A should be run,but not. If you summit another application B,when application B commplete, application A run .


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)