Return-Path: Delivered-To: apmail-lucene-hadoop-dev-archive@locus.apache.org Received: (qmail 75972 invoked from network); 17 Dec 2007 23:52:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 17 Dec 2007 23:52:05 -0000 Received: (qmail 62498 invoked by uid 500); 17 Dec 2007 23:51:53 -0000 Delivered-To: apmail-lucene-hadoop-dev-archive@lucene.apache.org Received: (qmail 62460 invoked by uid 500); 17 Dec 2007 23:51:53 -0000 Mailing-List: contact hadoop-dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: hadoop-dev@lucene.apache.org Delivered-To: mailing list hadoop-dev@lucene.apache.org Received: (qmail 62451 invoked by uid 99); 17 Dec 2007 23:51:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2007 15:51:53 -0800 X-ASF-Spam-Status: No, hits=-100.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO brutus.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Dec 2007 23:51:39 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 3676E714273 for ; Mon, 17 Dec 2007 15:51:43 -0800 (PST) Message-ID: <16698449.1197935503220.JavaMail.jira@brutus> Date: Mon, 17 Dec 2007 15:51:43 -0800 (PST) From: "Christian Kunz (JIRA)" To: hadoop-dev@lucene.apache.org Subject: [jira] Commented: (HADOOP-2119) JobTracker becomes non-responsive if the task trackers finish task too fast In-Reply-To: <30259449.1193690690792.JavaMail.jira@brutus> 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-2119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12552579 ] Christian Kunz commented on HADOOP-2119: ---------------------------------------- Because of the time required to produce a comprehensive patch, I changed the blocker to 0.16. > JobTracker becomes non-responsive if the task trackers finish task too fast > --------------------------------------------------------------------------- > > Key: HADOOP-2119 > URL: https://issues.apache.org/jira/browse/HADOOP-2119 > Project: Hadoop > Issue Type: Bug > Components: mapred > Affects Versions: 0.16.0 > Reporter: Runping Qi > Priority: Blocker > Fix For: 0.16.0 > > Attachments: hadoop-2119.patch, hadoop-jobtracker-thread-dump.txt > > > I ran a job with 0 reducer on a cluster with 390 nodes. > The mappers ran very fast. > The jobtracker lacks behind on committing completed mapper tasks. > The number of running mappers displayed on web UI getting bigger and bigger. > The jos tracker eventually stopped responding to web UI. > No progress is reported afterwards. > Job tracker is running on a separate node. > The job tracker process consumed 100% cpu, with vm size 1.01g (reach the heap space limit). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.