hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hadoop QA (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-3632) Ordering policy should be allowed to reorder an application when demand changes
Date Fri, 15 May 2015 04:26:00 GMT

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

Hadoop QA commented on YARN-3632:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  15m  3s | 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:red}-1{color} | javac |   7m 45s | The applied patch generated  1  additional warning
messages. |
| {color:green}+1{color} | javadoc |   9m 47s | There were no new javadoc warning messages.
|
| {color:green}+1{color} | release audit |   0m 22s | The applied patch does not increase
the total number of release audit warnings. |
| {color:red}-1{color} | checkstyle |   0m 57s | The applied patch generated  12 new checkstyle
issues (total was 178, now 190). |
| {color:red}-1{color} | whitespace |   0m  1s | The patch has 1  line(s) that end in whitespace.
Use git apply --whitespace=fix. |
| {color:green}+1{color} | install |   1m 35s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse.
|
| {color:red}-1{color} | findbugs |   1m 20s | The patch appears to introduce 1 new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | yarn tests |  50m  7s | Tests passed in hadoop-yarn-server-resourcemanager.
|
| | |  87m 34s | |
\\
\\
|| Reason || Tests ||
| FindBugs | module:hadoop-yarn-server-resourcemanager |
|  |  Inconsistent synchronization of org.apache.hadoop.yarn.server.resourcemanager.recovery.FileSystemRMStateStore.isHDFS;
locked 66% of time  Unsynchronized access at FileSystemRMStateStore.java:66% of time  Unsynchronized
access at FileSystemRMStateStore.java:[line 156] |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12733043/YARN-3632.3.patch |
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 9a2a955 |
| javac | https://builds.apache.org/job/PreCommit-YARN-Build/7948/artifact/patchprocess/diffJavacWarnings.txt
|
| checkstyle |  https://builds.apache.org/job/PreCommit-YARN-Build/7948/artifact/patchprocess/diffcheckstylehadoop-yarn-server-resourcemanager.txt
|
| whitespace | https://builds.apache.org/job/PreCommit-YARN-Build/7948/artifact/patchprocess/whitespace.txt
|
| Findbugs warnings | https://builds.apache.org/job/PreCommit-YARN-Build/7948/artifact/patchprocess/newPatchFindbugsWarningshadoop-yarn-server-resourcemanager.html
|
| hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7948/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7948/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/7948/console |


This message was automatically generated.

> Ordering policy should be allowed to reorder an application when demand changes
> -------------------------------------------------------------------------------
>
>                 Key: YARN-3632
>                 URL: https://issues.apache.org/jira/browse/YARN-3632
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>          Components: capacityscheduler
>            Reporter: Craig Welch
>            Assignee: Craig Welch
>         Attachments: YARN-3632.0.patch, YARN-3632.1.patch, YARN-3632.3.patch
>
>
> At present, ordering policies have the option to have an application re-ordered (for
allocation and preemption) when it is allocated to or a container is recovered from the application.
 Some ordering policies may also need to reorder when demand changes if that is part of the
ordering comparison, this needs to be made available (and used by the fairorderingpolicy when
sizebasedweight is true)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message