Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 28566 invoked from network); 3 Jul 2008 03:59:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 3 Jul 2008 03:59:07 -0000 Received: (qmail 56480 invoked by uid 500); 3 Jul 2008 03:59:07 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 56470 invoked by uid 500); 3 Jul 2008 03:59:07 -0000 Mailing-List: contact core-dev-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-dev@hadoop.apache.org Delivered-To: mailing list core-dev@hadoop.apache.org Received: (qmail 56454 invoked by uid 99); 3 Jul 2008 03:59:07 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Jul 2008 20:59:07 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Jul 2008 03:58:24 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 365B0234C152 for ; Wed, 2 Jul 2008 20:58:45 -0700 (PDT) Message-ID: <675874244.1215057525221.JavaMail.jira@brutus> Date: Wed, 2 Jul 2008 20:58:45 -0700 (PDT) From: "Severin Hacker (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-707) Final map task gets stuck MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/HADOOP-707?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12610119#action_12610119 ] Severin Hacker commented on HADOOP-707: --------------------------------------- I think this is still valid. I see the same behavior. It is also related to HADOOP-3632. > Final map task gets stuck > ------------------------- > > Key: HADOOP-707 > URL: https://issues.apache.org/jira/browse/HADOOP-707 > Project: Hadoop Core > Issue Type: Bug > Components: mapred > Affects Versions: 0.8.0 > Environment: using latest trunk > Reporter: Johan Oskarsson > Assignee: Owen O'Malley > Priority: Critical > > I've seen numerous jobs lately where the final map task gets stuck, never finishing. > The jobtracker doesn't reassign the task. A restart of the tasktracker solves the issue and the job can finish. > In the web interface it turns up as: > task_0028_m_000534_0 node17.herd1 RUNNING 0.00% 10-Nov-2006 12:21:12 10-Nov-2006 12:22:19 (1mins, 6sec) > Task failed to report status for 604 seconds. Killing. > Only exception I find in that tasktracker log is this (a few times): > java.nio.channels.ClosedChannelException > at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:125) > at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:294) > at org.apache.hadoop.ipc.SocketChannelOutputStream.flushBuffer(SocketChannelOutputStream.java:108) > at org.apache.hadoop.ipc.SocketChannelOutputStream.write(SocketChannelOutputStream.java:89) > at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65) > at java.io.BufferedOutputStream.flush(BufferedOutputStream.java:123) > at java.io.DataOutputStream.flush(DataOutputStream.java:106) > at org.apache.hadoop.ipc.Server$Handler.run(Server.java:532) -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.