hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-263) task status should include timestamps for when a job transitions
Date Mon, 07 Aug 2006 06:21:15 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-263?page=all ]

Owen O'Malley updated HADOOP-263:

    Status: Open  (was: Patch Available)

A couple of points need work:
  1. It only catches the finish time of the task.
  2. It includes a couple of comment/whitespace changes that are accidental.
  3. It calls the added field "timestamp", which doesn't say what the time represents.

I was expecting to see:
  2 new fields in TaskStatus:
     private long timeStarted;
     private long timeStopped;
  a new class derived from TaskStatus named ReduceTaskStatus that includes:
     private long timeShuffleFinished;
     private long timeSortFinished;

This patch does point out the high simularity of the TaskStatus and TaskReport. They are basically
the same type just slightly filtered by which protocol they are being used on. Why don't you
add timeStarted and timeStopped to TaskReport and we can  drop TaskReport in a later patch.

> task status should include timestamps for when a job transitions
> ----------------------------------------------------------------
>                 Key: HADOOP-263
>                 URL: http://issues.apache.org/jira/browse/HADOOP-263
>             Project: Hadoop
>          Issue Type: Improvement
>          Components: mapred
>    Affects Versions: 0.2.1
>            Reporter: Owen O'Malley
>         Assigned To: Sanjay Dahiya
>             Fix For: 0.6.0
>         Attachments: patch.txt
> It would help users to understand what happened if the task status included information
about when the task transitioned:
> Map:
>    started
>    finished
> Reduce:
>    started
>    shuffle finished
>    sort finished
>    finished

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message