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

Posted to mapreduce-issues@hadoop.apache.org by "Devaraj K (JIRA)" <ji...@apache.org> on 2011/06/03 12:21:47 UTC

[jira] [Commented] (MAPREDUCE-2237) Lost heartbeat response containing MapTask throws NPE when it is resent

    [ https://issues.apache.org/jira/browse/MAPREDUCE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13043283#comment-13043283 ] 

Devaraj K commented on MAPREDUCE-2237:
--------------------------------------

These contrib test cases failures are not because of this patch.

> Lost heartbeat response containing MapTask throws NPE when it is resent
> -----------------------------------------------------------------------
>
>                 Key: MAPREDUCE-2237
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2237
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: jobtracker
>    Affects Versions: 0.20.2, 0.21.0, 0.22.0
>            Reporter: Todd Lipcon
>            Assignee: Devaraj K
>             Fix For: 0.20.4, 0.23.0
>
>         Attachments: MAPREDUCE-2237-0.20.patch, MAPREDUCE-2237-0.23.patch
>
>
> When the JT sends a heartbeat response, it records it in trackerToHeartbeatResponseMap. But after MapTask writes its input split, it sets that split to null (assumedly to save memory?). So, if the heartbeat response is lost, and the JT needs to resend it, it will throw NPE since the split information has been lost.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira