You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Thomas Graves (Updated) (JIRA)" <ji...@apache.org> on 2011/11/01 21:41:36 UTC
[jira] [Updated] (MAPREDUCE-3328) mapred queue -list output
inconsistent and missing child queues
[ https://issues.apache.org/jira/browse/MAPREDUCE-3328?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Graves updated MAPREDUCE-3328:
-------------------------------------
Description:
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%
Release Note: (was: 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%)
> 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
> Priority: Critical
>
> 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