hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Allen Wittenauer (JIRA)" <j...@apache.org>
Subject [jira] Updated: (MAPREDUCE-1755) Zombie tasks kept alive by logging system
Date Wed, 05 May 2010 19:17:08 GMT

     [ https://issues.apache.org/jira/browse/MAPREDUCE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Allen Wittenauer updated MAPREDUCE-1755:

    Attachment: tightloop.txt

Stripping out the threading info (pollsys, etc) shows that the tasks are in a tight loop around
manipulating the log files (see tightloop.txt).

I'm also attaching the syslog and stderr logs from this task to see if that helps to figure
out where we're missing a thread needing to get killed.

> 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: 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.
You can reply to this email to add a comment to the issue online.

View raw message