Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <30942496.29151273090023510.JavaMail.jira@thor>
Date: Wed, 5 May 2010 16:07:03 -0400 (EDT)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1755) Zombie tasks kept alive by
 logging system
In-Reply-To: <6035765.24991273079044480.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12864479#action_12864479 ] 

Todd Lipcon commented on MAPREDUCE-1755:
----------------------------------------

Do you have a jstack from the JVM?

> 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.