[ https://issues.apache.org/jira/browse/YARN-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13573165#comment-13573165 ]
nemon lou commented on YARN-374: -------------------------------- Thanks for the information. But why not have one more API like gracefullyKillApplication(or just change force kill's behavior). With this method,RM will ask AM to kill the app itself, a force kill will be triggered if AM haven't killed itself during some period. > Job History Server doesn't show jobs which killed by > ClientRMProtocol.forceKillApplication > ------------------------------------------------------------------------------------------ > > Key: YARN-374 > URL: https://issues.apache.org/jira/browse/YARN-374 > Project: Hadoop YARN > Issue Type: Bug > Components: client, resourcemanager > Affects Versions: 2.0.1-alpha > Reporter: nemon lou > > After i kill a app by typing "bin/yarn rmadmin app -kill APP_ID", > no job info is kept on JHS web page. > However, when i kill a job by typing " bin/mapred job -kill JOB_ID" , > i can see a killed job left on JHS. > Some hive users are confused by that their jobs been killed but nothing left > on JHS ,and killed app's info on RM web page is not enough.(They kill job by > clientRMProtocol) -- 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