Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 9074 invoked from network); 15 Dec 2008 13:06:09 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 15 Dec 2008 13:06:09 -0000 Received: (qmail 63765 invoked by uid 500); 15 Dec 2008 13:06:20 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 63474 invoked by uid 500); 15 Dec 2008 13:06:18 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 63214 invoked by uid 99); 15 Dec 2008 13:06:18 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2008 05:06:17 -0800 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Dec 2008 13:06:04 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 48847234C3DB for ; Mon, 15 Dec 2008 05:05:44 -0800 (PST) Message-ID: <1395803541.1229346344296.JavaMail.jira@brutus> Date: Mon, 15 Dec 2008 05:05:44 -0800 (PST) From: "Hadoop QA (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-4774) CapacityScheduler should work even if capacity-scheduler.xml is not in the classpath i.e with the code defaults In-Reply-To: <1324311924.1228393664234.JavaMail.jira@brutus> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-4774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12656618#action_12656618 ] Hadoop QA commented on HADOOP-4774: ----------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12396068/HADOOP-4774-3.patch against trunk revision 726129. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 5 new or modified tests. +1 javadoc. The javadoc tool did not generate any warning messages. +1 javac. The applied patch does not increase the total number of javac compiler warnings. +1 findbugs. The patch does not introduce any new Findbugs warnings. +1 Eclipse classpath. The patch retains Eclipse classpath integrity. +1 core tests. The patch passed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Hadoop-Patch/3745/console This message is automatically generated. > CapacityScheduler should work even if capacity-scheduler.xml is not in the classpath i.e with the code defaults > --------------------------------------------------------------------------------------------------------------- > > Key: HADOOP-4774 > URL: https://issues.apache.org/jira/browse/HADOOP-4774 > Project: Hadoop Core > Issue Type: Bug > Components: contrib/capacity-sched > Reporter: Amar Kamat > Assignee: Sreekanth Ramakrishnan > Attachments: HADOOP-4774-1.patch, HADOOP-4774-2.patch, HADOOP-4774-3.patch > > > If I try running capacity-scheduler without having capacity-scheduler.xml in my class path, the jobtracker fails with the following error > {code} > Invalid initializater poller interval -1 > {code} > I feel the problem lies with the default value assigned to it in the code. The capacity-scheduler conf says the default is 5000. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.