Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Mon, 28 Nov 2011 16:53:40 +0000 (UTC)
From: "Ravi Prakash (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <2056584950.18334.1322499220276.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


    [ https://issues.apache.org/jira/browse/MAPREDUCE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13158555#comment-13158555 ] 

Ravi Prakash commented on MAPREDUCE-3328:
-----------------------------------------

Mahadev,
TestMRCLI is failing without the patch too. There are JIRAs filed MAPREDUCE-2565 and MAPREDUCE-3207. 
                
> 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