[ https://issues.apache.org/jira/browse/MAPREDUCE-5502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13773357#comment-13773357 ]
Vrushali C commented on MAPREDUCE-5502: --------------------------------------- Sounds good, thanks! Uploading a patch with the suggested changes. (not setting to patch available yet since I want to add some tests). I added a isStateTerminal function in JobStatus.State to reduce the number of checks (i.e. status.getState() != JobStatus.State.KILLED && status.getState() != JobStatus.State.SUCCEEDED && status.getState() != JobStatus.State.FAILED. How do this look now > History link in resource manager is broken for KILLED jobs > ---------------------------------------------------------- > > Key: MAPREDUCE-5502 > URL: https://issues.apache.org/jira/browse/MAPREDUCE-5502 > Project: Hadoop Map/Reduce > Issue Type: Bug > Components: resourcemanager > Affects Versions: 2.0.5-alpha > Reporter: Vrushali C > Assignee: Vrushali C > Labels: ui > > History link in resource manager is broken for KILLED jobs. > Seems to happen with jobs with State 'KILLED' and FinalStatus 'KILLED'. If > the State is 'FINISHED' and FinalStatus is 'KILLED', then the "History" link > is fine. > It isn't easy to reproduce the problem since the time at which the app is > killed determines the state it ends up in, which is hard to guess. these > particular jobs seem to get a Diagnostics message of "Application killed by > user." where as the other killed jobs get " Kill Job received from client > job_1378766187901_0002 > Job received Kill while in RUNNING state. " -- 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