[ 
https://issues.apache.org/jira/browse/YARN-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Jonathan Eagles moved MAPREDUCE-5797 to YARN-1845:
--------------------------------------------------

          Component/s:     (was: webapps)
                           (was: jobhistoryserver)
     Target Version/s: 3.0.0, 2.5.0  (was: 0.23.11, 2.4.0)
    Affects Version/s:     (was: 0.23.9)
                       0.23.9
           Issue Type: Improvement  (was: Bug)
                  Key: YARN-1845  (was: MAPREDUCE-5797)
              Project: Hadoop YARN  (was: Hadoop Map/Reduce)

>  Elapsed time for failed tasks that never started is  wrong 
> ------------------------------------------------------------
>
>                 Key: YARN-1845
>                 URL: https://issues.apache.org/jira/browse/YARN-1845
>             Project: Hadoop YARN
>          Issue Type: Improvement
>    Affects Versions: 0.23.9
>            Reporter: Rushabh S Shah
>            Assignee: Rushabh S Shah
>         Attachments: MAPREDUCE-5797-v3.patch, patch-MapReduce-5797-v2.patch, 
> patch-MapReduce-5797-v2.patch, patch-MapReduce-5797.patch
>
>
> 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)

Reply via email to