Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Message-ID: <14247719.19481276643726747.JavaMail.jira@thor>
Date: Tue, 15 Jun 2010 19:15:26 -0400 (EDT)
From: "Allen Wittenauer (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Subject: [jira] Commented: (MAPREDUCE-1869) TaskTracker hung in
 org.apache.hadoop.fs.LocalDirAllocator
In-Reply-To: <13037231.18691276642643346.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-1869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12879172#action_12879172 ] 

Allen Wittenauer commented on MAPREDUCE-1869:
---------------------------------------------

Oh, one other thing:  no really interesting exceptions in the tasktracker log.  Just the normal jetty mapoutput craziness.

> TaskTracker hung in org.apache.hadoop.fs.LocalDirAllocator
> ----------------------------------------------------------
>
>                 Key: MAPREDUCE-1869
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-1869
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: tasktracker
>    Affects Versions: 0.20.2
>         Environment: Solaris 10 Update 7
> Java 1.6.0_14
>            Reporter: Allen Wittenauer
>            Priority: Critical
>         Attachments: jstack.txt, pstack.txt
>
>
> A TaskTracker process on our grid appears to be locked up and not sending heartbeats to the namenode.  Attaching jstack and pstack output.  Even tho the hangs appear to be in LocalDirAllocator, the local file system seems to be a-ok.  

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