You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-dev@hadoop.apache.org by "Devaraj Das (JIRA)" <ji...@apache.org> on 2007/04/03 10:55:32 UTC

[jira] Commented: (HADOOP-1183) MapTask completion not recorded properly at the Reducer's end

    [ https://issues.apache.org/jira/browse/HADOOP-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12486268 ] 

Devaraj Das commented on HADOOP-1183:
-------------------------------------

I agree with Owen that the fetcher needs some redesigning on those lines. But in any case, should anyone see reduce(s) hanging (with the fetcher continuously trying to fetch output from a failed/lost map), this patch should be applied.

> MapTask completion not recorded properly at the Reducer's end
> -------------------------------------------------------------
>
>                 Key: HADOOP-1183
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1183
>             Project: Hadoop
>          Issue Type: Bug
>          Components: mapred
>    Affects Versions: 0.12.2
>            Reporter: Devaraj Das
>         Assigned To: Devaraj Das
>            Priority: Critical
>             Fix For: 0.13.0
>
>         Attachments: 1183.new.patch, 1183.new1.patch, 1183.patch
>
>
> A couple of reducers were continuously trying to fetch map outputs from a lost tasktracker. Although the tasks running on that lost TT successfully reexecuted elsewhere, the Reducers' tasktrackers didn't correctly note those events.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.