[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Resolution: Not A Problem Status: Resolved (was: Patch Available) It is no more problem in active versions. 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.24.0 Attachments: MAPREDUCE-2237-0.20.patch, MAPREDUCE-2237-0.23.1.patch, MAPREDUCE-2237-0.23.2.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. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Attachment: MAPREDUCE-2237-0.23.2.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.23.0 Attachments: MAPREDUCE-2237-0.20.patch, MAPREDUCE-2237-0.23.1.patch, MAPREDUCE-2237-0.23.2.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
[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Status: Patch Available (was: Open) 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.2.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
[jira] [Updated] (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: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
[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Attachment: MAPREDUCE-2237-0.23.1.patch Updated the patch for trunk since it became stale. 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.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
[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Attachment: MAPREDUCE-2237-0.23.patch MAPREDUCE-2237-0.20.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 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
[jira] [Updated] (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:all-tabpanel ] Devaraj K updated MAPREDUCE-2237: - Fix Version/s: 0.23.0 0.20.4 Status: Patch Available (was: Open) Removed the assignment of null to splitMetaInfo in 0.23 and split in 0.20.4. Please review these changes. 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.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
