[ https://issues.apache.org/jira/browse/MAPREDUCE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12747800#action_12747800 ]
Hadoop QA commented on MAPREDUCE-824: ------------------------------------- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12417611/MAPREDUCE-824-6.patch against trunk revision 807640. +1 @author. The patch does not contain any @author tags. +1 tests included. The patch appears to include 16 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 release audit. The applied patch does not increase the total number of release audit warnings. -1 core tests. The patch failed core unit tests. +1 contrib tests. The patch passed contrib unit tests. Test results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/518/testReport/ Findbugs warnings: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/518/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html Checkstyle results: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/518/artifact/trunk/build/test/checkstyle-errors.html Console output: http://hudson.zones.apache.org/hudson/job/Mapreduce-Patch-vesta.apache.org/518/console This message is automatically generated. > Support a hierarchy of queues in the capacity scheduler > ------------------------------------------------------- > > Key: MAPREDUCE-824 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-824 > Project: Hadoop Map/Reduce > Issue Type: New Feature > Components: contrib/capacity-sched > Reporter: Hemanth Yamijala > Attachments: HADOOP-824-1.patch, HADOOP-824-2.patch, > HADOOP-824-3.patch, HADOOP-824-4.patch, HADOOP-824-5.patch, > MAPREDUCE-824-6.patch, MAPREDUCE-824-7.patch > > > Currently in Capacity Scheduler, cluster capacity is divided among the queues > based on the queue capacity. These queues typically represent an organization > and the capacity of the queue represents the capacity the organization is > entitled to. Most organizations are large and need to divide their capacity > among sub-organizations they have. Or they may want to divide the capacity > based on a category or type of jobs they run. This JIRA covers the > requirements and other details to provide the above feature. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.