[ https://issues.apache.org/jira/browse/YARN-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13592645#comment-13592645 ]
Hadoop QA commented on YARN-227: -------------------------------- {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12571954/YARN-227-branch-0.23.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:green}+1 tests included{color}. The patch appears to include 1 new or modified test files. {color:red}-1 one of tests included doesn't have a timeout.{color} {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 javadoc{color}. The javadoc tool did not generate any warning messages. {color:red}-1 eclipse:eclipse{color}. The patch failed to build with eclipse:eclipse. {color:green}+1 findbugs{color}. The patch does not introduce any new Findbugs (version 1.3.9) warnings. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 core tests{color}. The patch passed unit tests in hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-resourcemanager. {color:green}+1 contrib tests{color}. The patch passed contrib unit tests. Test results: https://builds.apache.org/job/PreCommit-YARN-Build/463//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/463//console This message is automatically generated. > Application expiration difficult to debug for end-users > ------------------------------------------------------- > > Key: YARN-227 > URL: https://issues.apache.org/jira/browse/YARN-227 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 0.23.3, 2.0.1-alpha > Reporter: Jason Lowe > Assignee: Jason Lowe > Labels: usability > Attachments: YARN-227-branch-0.23.patch, YARN-227.patch > > > When an AM attempt expires the AMLivelinessMonitor in the RM will kill the > job and mark it as failed. However there are no diagnostic messages set for > the application indicating that the application failed because of expiration. > Even if the AM logs are examined, it's often not obvious that the > application was externally killed. The only evidence of what happened to the > application is currently in the RM logs, and those are often not accessible > by users. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira