Return-Path: X-Original-To: apmail-hadoop-mapreduce-issues-archive@minotaur.apache.org Delivered-To: apmail-hadoop-mapreduce-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 9A74F9F8A for ; Mon, 14 Nov 2011 17:14:13 +0000 (UTC) Received: (qmail 15470 invoked by uid 500); 14 Nov 2011 17:14:13 -0000 Delivered-To: apmail-hadoop-mapreduce-issues-archive@hadoop.apache.org Received: (qmail 15425 invoked by uid 500); 14 Nov 2011 17:14:13 -0000 Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: mapreduce-issues@hadoop.apache.org Delivered-To: mailing list mapreduce-issues@hadoop.apache.org Received: (qmail 15372 invoked by uid 99); 14 Nov 2011 17:14:13 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2011 17:14:13 +0000 X-ASF-Spam-Status: No, hits=-2001.2 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Nov 2011 17:14:12 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 27E2C820AC for ; Mon, 14 Nov 2011 17:13:52 +0000 (UTC) Date: Mon, 14 Nov 2011 17:13:52 +0000 (UTC) From: "Hadoop QA (Commented) (JIRA)" To: mapreduce-issues@hadoop.apache.org Message-ID: <1015502987.27254.1321290832164.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1993167515.47350.1320179854226.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (MAPREDUCE-3328) mapred queue -list output inconsistent and missing child queues 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/MAPREDUCE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13149754#comment-13149754 ] Hadoop QA commented on MAPREDUCE-3328: -------------------------------------- +1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12503635/MAPREDUCE-3328.branch-0.23.patch against trunk revision . +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 9 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 (version 1.3.9) warnings. +1 release audit. The applied patch does not increase the total number of release audit warnings. +1 core tests. The patch passed unit tests in . +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1302//testReport/ Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1302//console This message is automatically generated. > mapred queue -list output inconsistent and missing child queues > --------------------------------------------------------------- > > Key: MAPREDUCE-3328 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-3328 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: mrv2 > Affects Versions: 0.23.0 > Reporter: Thomas Graves > Assignee: Ravi Prakash > Priority: Critical > Attachments: MAPREDUCE-3328.branch-0.23.patch > > > When running mapred queue -list on a 0.23.0 cluster with capacity scheduler configured with child queues. In my case I have queues default, test1, and test2. test1 has subqueues of a1, a2. test2 has subqueues of a3 and a4. > - the child queues do not show up > - The output of maximum capacity doesn't match the format of the current capacity and capacity. the latter two use float while the maximum is specified as int: > Queue Name : default > Queue State : running > Scheduling Info : queueName: "default", capacity: 0.7, maximumCapacity: 90.0, currentCapacity: 0.0, state: Q_RUNNING, > ====================== > Queue Name : test > Queue State : running > Scheduling Info : queueName: "test", capacity: 0.2, maximumCapacity: -1.0, currentCapacity: 0.0, state: Q_RUNNING, > ====================== > Queue Name : test2 > Queue State : running > Scheduling Info : queueName: "test2", capacity: 0.1, maximumCapacity: 5.0, currentCapacity: 0.0, state: Q_RUNNING, > ====================== > here default is configured to have capacity=70% and maximum capacity = 90% -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira