[
https://issues.apache.org/jira/browse/HADOOP-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Devaraj Das updated HADOOP-5233:
--------------------------------
Resolution: Fixed
Hadoop Flags: [Reviewed]
Status: Resolved (was: Patch Available)
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)
> Reducer not Succeded after 100%
> -------------------------------
>
> Key: HADOOP-5233
> URL: https://issues.apache.org/jira/browse/HADOOP-5233
> Project: Hadoop Core
> Issue Type: Bug
> Components: mapred
> Affects Versions: 0.19.0
> Reporter: Amareshwari Sriramadasu
> Assignee: Amareshwari Sriramadasu
> Priority: Blocker
> Fix For: 0.20.0, 0.21.0
>
> Attachments: patch-5233-1.txt, patch-5233-2.txt, patch-5233.txt
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
