Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <1480517993.1248189314965.JavaMail.jira@brutus>
Date: Tue, 21 Jul 2009 08:15:14 -0700 (PDT)
From: "Arun C Murthy (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-430) Task stuck in cleanup with
 OutOfMemoryErrors
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Arun C Murthy commented on MAPREDUCE-430:
-----------------------------------------

bq. No. The task alive and stuck. I think pingThread was sending updates without any problem.

That worries me. Do we know why the jvm did not shutdown? Where did we catch and ignore the OOMError? Is the ping thread not a daemon-thread?

> Task stuck in cleanup with OutOfMemoryErrors
> --------------------------------------------
>
>                 Key: MAPREDUCE-430
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-430
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>            Reporter: Amareshwari Sriramadasu
>            Assignee: Amar Kamat
>             Fix For: 0.20.1
>
>         Attachments: MAPREDUCE-430-v1.6-branch-0.20.patch, MAPREDUCE-430-v1.6.patch
>
>
> Obesrved a task with OutOfMemory error, stuck in cleanup.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.