hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Doug Cutting (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-263) task status should include timestamps for when a job transitions
Date Wed, 20 Sep 2006 21:25:24 GMT
     [ http://issues.apache.org/jira/browse/HADOOP-263?page=all ]

Doug Cutting updated HADOOP-263:

    Status: Open  (was: Patch Available)

I am uncomfortable using progress status strings to determine which phase a task is in.  Rather
we should have a proper API for this.  (This is similar to HADOOP-544, but different.)

Perhaps we should have an enum in ReduceTask named Phase.  TaskUmbilicalProtocol.progress()
could get a new 'int phase' parameter that would include the phase.ordinal() value.  Would
that work?

> 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
>         Attachments: Hadoop-263.patch, Hadoop-263_1.patch, Hadoop-263_2.patch, Hadoop-263_3.patch,
patch.txt, patch.txt, patch.txt, 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