[
https://issues.apache.org/jira/browse/MAPREDUCE-1720?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12976656#action_12976656
]
Harsh J Chouraria commented on MAPREDUCE-1720:
----------------------------------------------
I think that's a good idea. Jobs can be killed for a reason (say, hadoop job
-kill JobID <reason why we're killing it>?), which can be included into the
JobStatus data, same with the whois of the killer; but when it comes to
failure, how do we deduce the 'reason' of failure -- just task numbers as
explained in the MAPREDUCE-343 ticket?
I also think that for Unsuccessful Jobs, displaying map and reduce progress
percentages is not a good thing, as it is not very indicative of the actual
progress (Always shows 100 or 0). We could remove this and claim some good real
estate to display reasons (limited characters of it).
> '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.
