hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Devaraj K (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-2237) Lost heartbeat response containing MapTask throws NPE when it is resent
Date Thu, 08 Sep 2011 08:41:10 GMT

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

Devaraj K commented on MAPREDUCE-2237:

Thanks Arun for looking into the patch.

I have rebased the patch, and also changed the approach according to your suggestion.

> 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.23.0
>         Attachments: MAPREDUCE-2237-0.20.patch, MAPREDUCE-2237-0.23.1.patch, MAPREDUCE-2237-0.23.2.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


View raw message