hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Eagles (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-1845) Elapsed time for failed tasks that never started is wrong
Date Mon, 17 Mar 2014 16:49:44 GMT

    [ https://issues.apache.org/jira/browse/YARN-1845?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13938017#comment-13938017
] 

Jonathan Eagles commented on YARN-1845:
---------------------------------------

+1. lgtm. Thanks for the patch, Rushabh. Committing this to branch-2 and trunk.

>  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)

Mime
View raw message