[
https://issues.apache.org/jira/browse/MAPREDUCE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976645#action_12976645
]
Amar Kamat commented on MAPREDUCE-1720:
---------------------------------------
Should we name the column named "Reason" as "State" and add a "Reason" column
indicating the reason why the job was failed/killed? In the failed section, we
can mention the reason for failure (assuming the reason is stored in the job
status). As an improvement, we can mention some more details like who
[user+group] killed the job etc. Thoughts?
> 'Killed' jobs and 'Failed' jobs should be displayed seperately in JobTracker
> UI
> --------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1720
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1720
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: jobtracker
> Affects Versions: 0.20.1
> Environment: all
> Reporter: Subramaniam Krishnan
> Assignee: Harsh J Chouraria
> Fix For: 0.23.0
>
> Attachments: mapred.failed.killed.difference.png,
> mapreduce.unsuccessfuljobs.ui.r1.diff
>
>
> The JobTracker UI shows both Failed/Killed Jobs as Failed. The Killed job
> status has been separated from Failed as part of HADOOP-3924, so the UI needs
> to be updated to reflect the same.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
