[ https://issues.apache.org/jira/browse/YARN-3983?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14648178#comment-14648178 ]
Hadoop QA commented on YARN-3983: --------------------------------- \\ \\ | (x) *{color:red}-1 overall{color}* | \\ \\ || Vote || Subsystem || Runtime || Comment || | {color:blue}0{color} | pre-patch | 16m 11s | Pre-patch trunk compilation is healthy. | | {color:green}+1{color} | @author | 0m 0s | The patch does not contain any @author tags. | | {color:green}+1{color} | tests included | 0m 0s | The patch appears to include 1 new or modified test files. | | {color:green}+1{color} | javac | 7m 44s | There were no new javac warning messages. | | {color:green}+1{color} | javadoc | 9m 42s | There were no new javadoc warning messages. | | {color:red}-1{color} | release audit | 0m 19s | The applied patch generated 1 release audit warnings. | | {color:red}-1{color} | checkstyle | 0m 47s | The applied patch generated 30 new checkstyle issues (total was 54, now 55). | | {color:red}-1{color} | whitespace | 0m 2s | The patch has 16 line(s) that end in whitespace. Use git apply --whitespace=fix. | | {color:green}+1{color} | install | 1m 21s | mvn install still works. | | {color:green}+1{color} | eclipse:eclipse | 0m 33s | The patch built with eclipse:eclipse. | | {color:green}+1{color} | findbugs | 1m 24s | The patch does not introduce any new Findbugs (version 3.0.0) warnings. | | {color:red}-1{color} | yarn tests | 49m 29s | Tests failed in hadoop-yarn-server-resourcemanager. | | | | 87m 37s | | \\ \\ || Reason || Tests || | Failed unit tests | hadoop.yarn.server.resourcemanager.TestKillApplicationWithRMHA | | | hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRestart | | | hadoop.yarn.server.resourcemanager.ahs.TestRMApplicationHistoryWriter | | | hadoop.yarn.server.resourcemanager.scheduler.fair.TestAllocationFileLoaderService | | Timed out tests | org.apache.hadoop.yarn.server.resourcemanager.applicationsmanager.TestAMRMRPCNodeUpdates | \\ \\ || Subsystem || Report/Notes || | Patch URL | http://issues.apache.org/jira/secure/attachment/12748038/YARN-3983.2.patch | | Optional Tests | javadoc javac unit findbugs checkstyle | | git revision | trunk / 91b42e7 | | Release Audit | https://builds.apache.org/job/PreCommit-YARN-Build/8720/artifact/patchprocess/patchReleaseAuditProblems.txt | | checkstyle | https://builds.apache.org/job/PreCommit-YARN-Build/8720/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt | | whitespace | https://builds.apache.org/job/PreCommit-YARN-Build/8720/artifact/patchprocess/whitespace.txt | | hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/8720/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt | | Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/8720/testReport/ | | Java | 1.7.0_55 | | uname | Linux asf903.gq1.ygridcore.net 3.13.0-36-lowlatency #63-Ubuntu SMP PREEMPT Wed Sep 3 21:56:12 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux | | Console output | https://builds.apache.org/job/PreCommit-YARN-Build/8720/console | This message was automatically generated. > Make CapacityScheduler to easier extend application allocation logic > -------------------------------------------------------------------- > > Key: YARN-3983 > URL: https://issues.apache.org/jira/browse/YARN-3983 > Project: Hadoop YARN > Issue Type: Bug > Reporter: Wangda Tan > Assignee: Wangda Tan > Attachments: YARN-3983.1.patch, YARN-3983.2.patch > > > While working on YARN-1651 (resource allocation for increasing container), I > found it is very hard to extend existing CapacityScheduler resource > allocation logic to support different types of resource allocation. > For example, there's a lot of differences between increasing a container and > allocating a container: > - Increasing a container doesn't need to check locality delay. > - Increasing a container doesn't need to build/modify a resource request tree > (ANY->RACK/HOST). > - Increasing a container doesn't need to check allocation/reservation > starvation (see {{shouldAllocOrReserveNewContainer}}). > - After increasing a container is approved by scheduler, it need to update an > existing container token instead of creating new container. > And there're lots of similarities when allocating different types of > resources. > - User-limit/queue-limit will be enforced for both of them. > - Both of them needs resource reservation logic. (Maybe continuous > reservation looking is needed for both of them). > The purpose of this JIRA is to make easier extending CapacityScheduler > resource allocation logic to support different types of resource allocation, > make common code reusable, and also better code organization. -- This message was sent by Atlassian JIRA (v6.3.4#6332)