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 "Todd Lipcon (JIRA)" <ji...@apache.org> on 2011/07/06 03:32:16 UTC
[jira] [Commented] (MAPREDUCE-2429) Check jvmid during task status
report
[ https://issues.apache.org/jira/browse/MAPREDUCE-2429?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13060229#comment-13060229 ]
Todd Lipcon commented on MAPREDUCE-2429:
----------------------------------------
The version of this patch on 0.20-security seems to have a bug in that it doesn't call task.setJvmContext() until after the syncLogs call, etc. Thus, if syncLogs fails, jvmContext is still null, and the status update will have null Jvmcontext, causing NPE. The patch against trunk seems to have fixed this by calling setJvmContext at the top.
> Check jvmid during task status report
> -------------------------------------
>
> Key: MAPREDUCE-2429
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-2429
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: tasktracker
> Affects Versions: 0.21.0, 0.22.0, 0.23.0
> Reporter: Arun C Murthy
> Assignee: Siddharth Seth
> Fix For: 0.20.204.0, 0.23.0
>
> Attachments: MR2429-1.patch, MR2429.patch, MR2429_trunk.patch
>
>
> Currently TT doens't check to ensure jvmid is relevant during communication with the Child via TaskUmbilicalProtocol.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira