Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 14 Mar 2014 22:06:42 +0000 (UTC)
From: "Rushabh S Shah (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12701567.1394825599315.73492.1394834802923@arcas>
In-Reply-To: <JIRA.12701567.1394825599315@arcas>
References: <JIRA.12701567.1394825599315@arcas>
Subject: [jira] [Updated] (MAPREDUCE-5797)  Elapsed time for failed tasks
 that never started is  wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Rushabh S Shah updated MAPREDUCE-5797:
--------------------------------------

    Status: Patch Available  (was: Open)

Added Apache License Agreement TestTimes.java

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