[ http://issues.apache.org/jira/browse/HADOOP-263?page=all ]
Sanjay Dahiya updated HADOOP-263:
---------------------------------
Attachment: Hadoop-263_4.patch
Here is an updated patch, as doug suggested I have added an extra argument to
TaskUmbilicalProtocol.progress(String taskid, float progress, String state, int
phase). phase is Phase.ordinal().
All classes deriving from TaskUmbilicalProtocol are updated with this argument,
but its value is ignored in IsolationRunner and LocalJobRunner.
In JobTracker.ExpireLaunchingTasks.run() the phase is not available if its a
reduce task, in such case it uses Phase.UNKNOWN.
Also both map and reduce tasks use TaskUmbilicalProtocol.progress, so Map tasks
return Phase.MAP and reduce tasks return Phase.SHUFFLE, PHASE.SORT or
Phase.REDUCE.
> 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, Hadoop-263_4.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
