hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amareshwari Sriramadasu (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-5233) Reducer not Succeded after 100%
Date Fri, 20 Feb 2009 10:37:01 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-5233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Amareshwari Sriramadasu updated HADOOP-5233:

    Fix Version/s:     (was: 0.19.1)
           Status: Patch Available  (was: Open)

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

> 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
> 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.

View raw message