[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164359#comment-13164359 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Hdfs-HAbranch-build #8 (See [https://builds.apache.org/job/Hadoop-Hdfs-HAbranch-build/8/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) - Merging r1211243 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211247 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164361#comment-13164361 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Hdfs-0.23-Build #100 (See [https://builds.apache.org/job/Hadoop-Hdfs-0.23-Build/100/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) - Merging r1211243 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211247 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164367#comment-13164367 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Hdfs-trunk #887 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk/887/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211243 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164375#comment-13164375 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Mapreduce-0.23-Build #118 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Build/118/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) - Merging r1211243 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211247 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164388#comment-13164388 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Mapreduce-trunk #920 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk/920/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211243 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164000#comment-13164000 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Common-trunk-Commit #1374 (See [https://builds.apache.org/job/Hadoop-Common-trunk-Commit/1374/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211243 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164001#comment-13164001 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Hdfs-trunk-Commit #1446 (See [https://builds.apache.org/job/Hadoop-Hdfs-trunk-Commit/1446/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211243 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164019#comment-13164019 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Mapreduce-trunk-Commit #1398 (See [https://builds.apache.org/job/Hadoop-Mapreduce-trunk-Commit/1398/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211243 Files : * /hadoop/common/trunk/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/trunk/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13164034#comment-13164034 ] Hudson commented on MAPREDUCE-3147: --- Integrated in Hadoop-Mapreduce-0.23-Commit #266 (See [https://builds.apache.org/job/Hadoop-Mapreduce-0.23-Commit/266/]) MAPREDUCE-3147. Handle leaf queues with the same name properly. (Ravi Prakash via mahadev) - Merging r1211243 from trunk. mahadev : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVNview=revrev=1211247 Files : * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/CHANGES.txt * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/main/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/CapacityScheduler.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestApplicationLimits.java * /hadoop/common/branches/branch-0.23/hadoop-mapreduce-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager/src/test/java/org/apache/hadoop/yarn/server/resourcemanager/scheduler/capacity/TestCapacityScheduler.java Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13158551#comment-13158551 ] Hadoop QA commented on MAPREDUCE-3147: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12505340/MAPREDUCE-3147.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 6 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 appears to introduce 12 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/1347//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1347//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1347//console This message is automatically generated. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13158718#comment-13158718 ] Ravi Prakash commented on MAPREDUCE-3147: - The findbugs warning is not related to this patch. The same patch also applies to trunk. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154461#comment-13154461 ] Hadoop QA commented on MAPREDUCE-3147: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12504536/MAPREDUCE-3147.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 3 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 appears to introduce 12 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/1332//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1332//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-mapreduce-examples.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1332//console This message is automatically generated. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13154487#comment-13154487 ] Ravi Prakash commented on MAPREDUCE-3147: - None of the findbugs warning relate to this patch. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13151511#comment-13151511 ] Nathan Roberts commented on MAPREDUCE-3147: --- I thought about this a bit further. I wish we had a clearer separation between: * leaf queues - queues which jobs can be submitted against * parent queues - used to manage resources for a set of leaf nodes I think users will get confused by the fact that you can't have a configuration with root.a.b and root.c.b. If the job submission queues had been kept separate and then a property of the job submission queue described where they attach to the resource hierarchy, it might have been clearer. That way it's very clear where jobs can be submitted, and it's clear that the list of queues where jobs can be submitted is a flat namespace, and it's clear that the hierarchical part of the resource management can be reconfigured without any change to where jobs actually get submitted. However, the additional gain of making this sort of change to the way queues are defined doesn't seem worth it. We'll just have to be very clear in the documentation that the namespace of the leaves is flat. This Jira can be used to prevent the RM from accepting configurations where there is a conflict in the list of job submission queues. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150691#comment-13150691 ] Mahadev konar commented on MAPREDUCE-3147: -- Ravi, Am a little confused. So now the jobs need to submit to root.a.b.c.d? unlike just d as it used to be? Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150709#comment-13150709 ] Hadoop QA commented on MAPREDUCE-3147: -- -1 overall. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12503780/MAPREDUCE-3147.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 6 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 appears to introduce 1 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 failed these unit tests: org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestParentQueue org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.TestApplicationLimits +1 contrib tests. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1308//testReport/ Findbugs warnings: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1308//artifact/trunk/hadoop-mapreduce-project/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html Console output: https://builds.apache.org/job/PreCommit-MAPREDUCE-Build/1308//console This message is automatically generated. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150711#comment-13150711 ] Ravi Prakash commented on MAPREDUCE-3147: - Hi Mahadev, Sorry I typoed in the last comment. Jobs can still be submitted to a.b.c.d (rather than root.a.b.c.d). Just submitting to 'd' wouldn't work. The reason for this change is that if there were two queues configured root.a.b.c.d and root.x.y.z.d then to disambiguate you would NEED to specify the whole path. Nathan was in favor of using whole path names rather than disallowing two leaf queues to have the same name. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150816#comment-13150816 ] Arun C Murthy commented on MAPREDUCE-3147: -- We should keep queue names unique and not change the interface. I'll close this as a won't fix? Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150815#comment-13150815 ] Arun C Murthy commented on MAPREDUCE-3147: -- I don't think we should change this at all... this will be a big incompatible change for users. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150866#comment-13150866 ] Ravi Prakash commented on MAPREDUCE-3147: - Arun! At the very least we should prevent leaf queues from having the same name. So if there are two queues configured root.a.b.c.d and root.x.y.z.d Then there is no way for a user to submit their job to a.b.c.d. (Currently the lookup table is overwritten with the last parsed queue name) Can you please explain why this would be an incompatible change? Were multi-level hierarchical queues supported before? If they were, then this would be an incompatible change. However if they were not, the first level of queues would have the same name as always. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13150985#comment-13150985 ] Nathan Roberts commented on MAPREDUCE-3147: --- What I would like to avoid is one subtree limiting the namespace of another. One of the selling points behind the hierarchical queue structure is that an owner of a subtree can manage that subtree independently of the others. If the leaves of the tree are required to have globally unique names, it doesn't seem like we're quite meeting that goal (my subtree can't add a queue called default, if someone else has already taken that name). Is there no way we can maintain compatibility AND get to independent namespaces? Could we support the concept of an alias whereby relative queue names can be linked into the hierarchy d-root.a.b.c.d? Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 Attachments: MAPREDUCE-3147.branch-0.23.patch, MAPREDUCE-3147.branch-0.23.patch If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
[jira] [Commented] (MAPREDUCE-3147) Handle leaf queues with the same name properly
[ https://issues.apache.org/jira/browse/MAPREDUCE-3147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13149715#comment-13149715 ] Ravi Prakash commented on MAPREDUCE-3147: - There are two approaches to solve this problem: 1. Disallow queues with the same name. 2. Use the complete hierarchical name when specifying queues. Do any of you have comments which way it ought to be fixed? I'm leaning towards option 2. Handle leaf queues with the same name properly -- Key: MAPREDUCE-3147 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3147 Project: Hadoop Map/Reduce Issue Type: Improvement Components: mrv2 Affects Versions: 0.23.0 Reporter: Ravi Prakash Assignee: Ravi Prakash Fix For: 0.23.1 If there are two leaf queues with the same name, there is ambiguity while submitting jobs, displaying queue info. When such ambiguity exists, the system should ask for clarification / show disambiguated information. -- 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
