[
https://issues.apache.org/jira/browse/MAPREDUCE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980227#action_12980227
]
Harsh J Chouraria commented on MAPREDUCE-1720:
----------------------------------------------
I actually like the concept of having all (retained) jobs listed in one page.
This way, if you are monitoring one, and it actually fails or is killed, it
still remains on the same page; not requiring an inquisitive search for where
it really went. With browser search, one can also lookup the ID on a single
page, without having to switch any context for the resultant state (be it tab
or page). But yes, the representation could use a little work as the pages tend
to get longer and longer over load/time.
About job history/details, since the current job details page gets pretty large
thanks to counters and charts, it wouldn't look good even if it were expanded
inline, I think. Although we can have a short summary (defn.?) which can be
shown inline when clicked/hovered.
> '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.
