[
https://issues.apache.org/jira/browse/MAPREDUCE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Allen Wittenauer resolved MAPREDUCE-1755.
-----------------------------------------
Resolution: Won't Fix
It is easier to just pkill -9 java tasks at regular intervals than fix this.
> Zombie tasks kept alive by logging system
> -----------------------------------------
>
> Key: MAPREDUCE-1755
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1755
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Affects Versions: 0.20.2
> Reporter: Allen Wittenauer
> Attachments: jstack.txt, stderr.txt, syslog.txt, tightloop.txt
>
>
> I'm currently looking at a task that, as far as the task tracker is
> concerned, is dead. Like long long long ago dead. It was a failed task that
> ran out of heap. Rather than just kill it, I thought I would see what it was
> doing, since it was clearly using system resources. It would appear the
> system is trying to log but failing. I'm guessing we're missing an error
> condition and not doing the appropriate thing. See the comments for more.
--
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
