hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rushabh S Shah (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (MAPREDUCE-5797) Elapsed time for failed tasks that never started is wrong
Date Mon, 17 Mar 2014 16:09:44 GMT

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

Rushabh S Shah updated MAPREDUCE-5797:

    Attachment: MAPREDUCE-5797-v3.patch

>  Elapsed time for failed tasks that never started is  wrong 
> ------------------------------------------------------------
>                 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
>         Attachments: MAPREDUCE-5797-v3.patch, patch-MapReduce-5797-v2.patch, patch-MapReduce-5797-v2.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

View raw message