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-3543) ApplicationReport should be able to tell whether the Application is AM managed or not.
Date Tue, 12 May 2015 12:01:00 GMT

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

Hadoop QA commented on YARN-3543:
---------------------------------

\\
\\
| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | pre-patch |  15m 10s | 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 7 new
or modified test files. |
| {color:green}+1{color} | javac |   7m 47s | There were no new javac warning messages. |
| {color:green}+1{color} | javadoc |   9m 53s | 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:green}+1{color} | checkstyle |   3m 28s | There were no new checkstyle issues. |
| {color:green}+1{color} | whitespace |   0m  7s | The patch has no lines that end in whitespace.
|
| {color:green}+1{color} | install |   1m 37s | mvn install still works. |
| {color:green}+1{color} | eclipse:eclipse |   0m 33s | The patch built with eclipse:eclipse.
|
| {color:green}+1{color} | findbugs |   6m 28s | The patch does not introduce any new Findbugs
(version 2.0.3) warnings. |
| {color:green}+1{color} | yarn tests |   0m 26s | Tests passed in hadoop-yarn-api. |
| {color:green}+1{color} | yarn tests |   7m  8s | Tests passed in hadoop-yarn-client. |
| {color:green}+1{color} | yarn tests |   1m 58s | Tests passed in hadoop-yarn-common. |
| {color:green}+1{color} | yarn tests |   3m 10s | Tests passed in hadoop-yarn-server-applicationhistoryservice.
|
| {color:green}+1{color} | yarn tests |   0m 29s | Tests passed in hadoop-yarn-server-common.
|
| {color:red}-1{color} | yarn tests |  51m 48s | Tests failed in hadoop-yarn-server-resourcemanager.
|
| | | 110m 28s | |
\\
\\
|| Reason || Tests ||
| Failed unit tests | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerQueueACLs
|
|   | hadoop.yarn.server.resourcemanager.TestRM |
|   | hadoop.yarn.server.resourcemanager.TestApplicationACLs |
|   | hadoop.yarn.server.resourcemanager.TestClientRMService |
|   | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestNodeLabelContainerAllocation
|
|   | hadoop.yarn.server.resourcemanager.scheduler.fair.TestFairSchedulerQueueACLs |
|   | hadoop.yarn.server.resourcemanager.security.TestClientToAMTokens |
|   | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacitySchedulerDynamicBehavior
|
|   | hadoop.yarn.server.resourcemanager.scheduler.capacity.TestCapacityScheduler |
\\
\\
|| Subsystem || Report/Notes ||
| Patch URL | http://issues.apache.org/jira/secure/attachment/12732205/0003-YARN-3543.patch
|
| Optional Tests | javadoc javac unit findbugs checkstyle |
| git revision | trunk / 360dff5 |
| hadoop-yarn-api test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-api.txt
|
| hadoop-yarn-client test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-client.txt
|
| hadoop-yarn-common test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-common.txt
|
| hadoop-yarn-server-applicationhistoryservice test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-server-applicationhistoryservice.txt
|
| hadoop-yarn-server-common test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-server-common.txt
|
| hadoop-yarn-server-resourcemanager test log | https://builds.apache.org/job/PreCommit-YARN-Build/7882/artifact/patchprocess/testrun_hadoop-yarn-server-resourcemanager.txt
|
| Test Results | https://builds.apache.org/job/PreCommit-YARN-Build/7882/testReport/ |
| Java | 1.7.0_55 |
| uname | Linux asf904.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/7882/console |


This message was automatically generated.

> ApplicationReport should be able to tell whether the Application is AM managed or not.

> ---------------------------------------------------------------------------------------
>
>                 Key: YARN-3543
>                 URL: https://issues.apache.org/jira/browse/YARN-3543
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: api
>    Affects Versions: 2.6.0
>            Reporter: Spandan Dutta
>            Assignee: Rohith
>              Labels: BB2015-05-TBR
>         Attachments: 0001-YARN-3543.patch, 0001-YARN-3543.patch, 0002-YARN-3543.patch,
0002-YARN-3543.patch, 0003-YARN-3543.patch, 0003-YARN-3543.patch, YARN-3543-AH.PNG, YARN-3543-RM.PNG
>
>
> Currently we can know whether the application submitted by the user is AM managed from
the applicationSubmissionContext. This can be only done  at the time when the user submits
the job. We should have access to this info from the ApplicationReport as well so that we
can check whether an app is AM managed or not anytime.



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

Mime
View raw message