You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Rushabh S Shah (JIRA)" <ji...@apache.org> on 2014/03/14 20:34:42 UTC
[jira] [Created] (MAPREDUCE-5797) The elapsed time for tasks in a
failed job that were never started can be way off.
Rushabh S Shah created MAPREDUCE-5797:
-----------------------------------------
Summary: The elapsed time for tasks in a failed job that were never started can be way off.
Key: MAPREDUCE-5797
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5797
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: jobhistoryserver, webapps
Affects Versions: 0.23.9
Reporter: Rushabh S Shah
Assignee: Rushabh S Shah
The elapsed time for tasks in a failed job that were never
started can be way off. It looks like we're marking the start time as the
beginning of the epoch (i.e.: start time = -1) but the finish time is when the
task was marked as failed when the whole job failed. That causes the
calculated elapsed time of the task to be a ridiculous number of hours.
Tasks that fail without any attempts shouldn't have start/finish/elapsed times.
--
This message was sent by Atlassian JIRA
(v6.2#6252)