From yarn-issues-return-892-apmail-hadoop-yarn-issues-archive=hadoop.apache.org@hadoop.apache.org Thu Oct 4 18:53:48 2012 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 11FA0DC91 for ; Thu, 4 Oct 2012 18:53:48 +0000 (UTC) Received: (qmail 80301 invoked by uid 500); 4 Oct 2012 18:53:48 -0000 Delivered-To: apmail-hadoop-yarn-issues-archive@hadoop.apache.org Received: (qmail 80256 invoked by uid 500); 4 Oct 2012 18:53:47 -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 80246 invoked by uid 99); 4 Oct 2012 18:53:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2012 18:53:47 +0000 Date: Fri, 5 Oct 2012 05:53:47 +1100 (NCT) From: "Ahmed Radwan (JIRA)" To: yarn-issues@hadoop.apache.org Message-ID: <565401527.1228.1349376827913.JavaMail.jiratomcat@arcas> In-Reply-To: <1155499478.155352.1349200627789.JavaMail.jiratomcat@arcas> Subject: [jira] [Updated] (YARN-140) Add capacity-scheduler-default.xml to provide a default set of configurations for the capacity scheduler. 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-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ahmed Radwan updated YARN-140: ------------------------------ Attachment: YARN-140_rev2.patch Here is a new version of the patch that does the following: - Addresses the getCapacity for the root queue, and modifies the test to verify it (the patch from YARN-143). - Move capacity-scheduler.xml to hadoop-yarn-project/hadoop-yarn/conf/., so it will now be available in the conf directory in our distribution (etc/hadoop). - Removes the incorrectly placed capacity-scheduler.xml from hadoop-common-project. I have verified that TestCapacityScheduler runs successfully after these changes. > Add capacity-scheduler-default.xml to provide a default set of configurations for the capacity scheduler. > --------------------------------------------------------------------------------------------------------- > > Key: YARN-140 > URL: https://issues.apache.org/jira/browse/YARN-140 > Project: Hadoop YARN > Issue Type: Bug > Components: capacityscheduler > Reporter: Ahmed Radwan > Assignee: Ahmed Radwan > Attachments: YARN-140.patch, YARN-140_rev2.patch > > > When setting up the capacity scheduler users are faced with problems like: > {code} > FATAL org.apache.hadoop.yarn.server.resourcemanager.ResourceManager: Error starting ResourceManager > java.lang.IllegalArgumentException: Illegal capacity of -1 for queue root > {code} > Which basically arises from missing basic configurations, which in many cases, there is no need to explicitly provide, and a default configuration will be sufficient. For example, to address the error above, the user need to add a capacity of 100 to the root queue. > So, we need to add a capacity-scheduler-default.xml, this will be helpful to provide the basic set of default configurations required to run the capacity scheduler. The user can still override existing configurations or provide new ones in capacity-scheduler.xml. This is similar to *-default.xml vs *-site.xml for yarn, core, mapred, hdfs, etc. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira