Details

Description

I have seen a reducer in RUNNING state, when it was waiting for the commitResponse.
Task logs show :
2009-02-12 08:35:36,414 INFO org.apache.hadoop.mapred.TaskRunner: Task:attempt_200902120746_0297_r_000033_0 is done. And is in the process of commiting
and no logs after that.
TT logs say:
2009-02-12 08:35:36,417 INFO org.apache.hadoop.mapred.TaskTracker: Task attempt_200902120746_0297_r_000033_0 is in COMMIT_PENDING
2009-02-12 08:35:36,417 INFO org.apache.hadoop.mapred.TaskTracker: attempt_200902120746_0297_r_000033_0 0.33333334% reduce > sort

This looks like, the task progress went from COMMIT_PENDING to RUNNING again.

Amareshwari Sriramadasu
added a comment - 13/Feb/09 04:34 I would like to submit one patch for HADOOP-5233 , hADOOP-5234 and HADOOP-5235 , since they involve one line changes. This would lessen testing overhead.

[exec]
[exec] -1 overall.
[exec]
[exec] +1 @author. The patch does not contain any @author tags.
[exec]
[exec] -1 tests included. The patch doesn't appear to include any new or modified tests.
[exec] Please justify why no tests are needed for this patch.
[exec]
[exec] +1 javadoc. The javadoc tool did not generate any warning messages.
[exec]
[exec] +1 javac. The applied patch does not increase the total number of javac compiler warnings.
[exec]
[exec] +1 findbugs. The patch does not introduce any new Findbugs warnings.
[exec]
[exec] +1 Eclipse classpath. The patch retains Eclipse classpath integrity.
[exec]
[exec] +1 release audit. The applied patch does not increase the total number of release audit warnings.
[exec]

Devaraj Das
added a comment - 20/Feb/09 13:18 I just committed this to the 0.20 branch and trunk. Thanks, Amareshwari! (After 0.19.1 is released for which voting is going on, we should commit this to 0.19 branch as well)