Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Not A Problem
-
0.20.2, 0.21.0, 0.22.0
-
None
-
None
Description
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.
Attachments
Attachments
Issue Links
- is duplicated by
-
MAPREDUCE-2464 NullPointerException is coming in the job tracker when job tracker resends the previous heartbeat response.
- Resolved