[
https://issues.apache.org/jira/browse/MAPREDUCE-2237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated MAPREDUCE-2237:
-------------------------------------
Status: Open (was: Patch Available)
Sorry, patch has gone stale.
Also, we made this change long ago because splits were taking up memory in the
JT and were causing OOMs. Maybe we can reinit the split if it's null rather
than the current approach?
> 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.21.0, 0.20.2, 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.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
