[
https://issues.apache.org/jira/browse/HADOOP-2016?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arun C Murthy updated HADOOP-2016:
----------------------------------
Attachment: HADOOP-2016_2_20071011.patch
I figured that a less intrusive approach to just ignore the child's
status-update and not asking it to kill itself right-away would work as well. A
more conservation option.
> Race condition in removing a KILLED task from tasktracker
> ---------------------------------------------------------
>
> Key: HADOOP-2016
> URL: https://issues.apache.org/jira/browse/HADOOP-2016
> Project: Hadoop
> Issue Type: Bug
> Components: mapred
> Reporter: Devaraj Das
> Assignee: Arun C Murthy
> Priority: Blocker
> Fix For: 0.15.0
>
> Attachments: HADOOP-2016_20071011.patch, HADOOP-2016_2_20071011.patch
>
>
> I ran into a situation where a speculative task was killed by the JobTracker
> and the relevant TaskTracker got the right KillTaskAction, but the
> tasktracker continued to hold a reference to that task (although the task jvm
> was killed). The task continued to be in RUNNING state in both the JobTracker
> and that TaskTracker for ever. I suspect there is some race condition in
> reading/updating datastructures inside the taskCleanupThread &
> transmitHeartBeat.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
