[ https://issues.apache.org/jira/browse/YARN-337?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13733612#comment-13733612 ]
Hadoop QA commented on YARN-337: -------------------------------- {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12596859/YARN-337.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: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:green}+1 eclipse:eclipse{color}. The patch built 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/1675//testReport/ Console output: https://builds.apache.org/job/PreCommit-YARN-Build/1675//console This message is automatically generated. > RM handles killed application tracking URL poorly > ------------------------------------------------- > > Key: YARN-337 > URL: https://issues.apache.org/jira/browse/YARN-337 > Project: Hadoop YARN > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.0.2-alpha, 0.23.5 > Reporter: Jason Lowe > Assignee: Jason Lowe > Labels: usability > Attachments: YARN-337.patch > > > When the ResourceManager kills an application, it leaves the proxy URL > redirecting to the original tracking URL for the application even though the > ApplicationMaster is no longer there to service it. It should redirect it > somewhere more useful, like the RM's web page for the application, where the > user can find that the application was killed and links to the AM logs. > In addition, sometimes the AM during teardown from the kill can attempt to > unregister and provide an updated tracking URL, but unfortunately the RM has > "forgotten" the AM due to the kill and refuses to process the unregistration. > Instead it logs: > {noformat} > 2013-01-09 17:37:49,671 [IPC Server handler 2 on 8030] ERROR > org.apache.hadoop.yarn.server.resourcemanager.ApplicationMasterService: > AppAttemptId doesnt exist in cache appattempt_1357575694478_28614_000001 > {noformat} > It should go ahead and process the unregistration to update the tracking URL > since the application offered it. -- 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