[
https://issues.apache.org/jira/browse/MAPREDUCE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976667#action_12976667
]
Amar Kamat commented on MAPREDUCE-1720:
---------------------------------------
I think the reason for keeping the % information in the failed section is to
keep the table consistent with the running jobs table. I would like to know
what other think about this. Maybe as an enhancement, we can separate out
running/failed/killed jobs into separate tabs (jsp tabs?). Going forward, we
might want to display some statistics related to each section which should not
clutter the main (navigation?) page. History can also be displayed as one of
the tabs.
> '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.
