Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 43800 invoked from network); 27 Jun 2008 02:11:10 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 27 Jun 2008 02:11:10 -0000 Received: (qmail 45579 invoked by uid 500); 27 Jun 2008 02:11:08 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 45546 invoked by uid 500); 27 Jun 2008 02:11:08 -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 45534 invoked by uid 99); 27 Jun 2008 02:11:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 26 Jun 2008 19:11:08 -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; Fri, 27 Jun 2008 02:10:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id AF56A234C14D for ; Thu, 26 Jun 2008 19:10:46 -0700 (PDT) Message-ID: <1496510681.1214532646717.JavaMail.jira@brutus> Date: Thu, 26 Jun 2008 19:10:46 -0700 (PDT) From: "Konstantin Shvachko (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-3633) Uncaught exception in DataXceiveServer In-Reply-To: <421071322.1214351025070.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-3633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-3633: ---------------------------------------- Priority: Blocker (was: Major) Fix Version/s: 0.18.0 Should be fixed in 0.18. We see this rather regularly when many cluster nodes get full. > Uncaught exception in DataXceiveServer > -------------------------------------- > > Key: HADOOP-3633 > URL: https://issues.apache.org/jira/browse/HADOOP-3633 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.17.0 > Environment: 17.0 + H1979-H2159-H3442 > Reporter: Koji Noguchi > Priority: Blocker > Fix For: 0.18.0 > > Attachments: jstack-H3633.txt > > > Observed dfsclients timing out to some datanodes. > Datanode's '.out' file had > {noformat} > Exception in thread "org.apache.hadoop.dfs.DataNode$DataXceiveServer@82d37" java.lang.OutOfMemoryError: unable to create new native thread > at java.lang.Thread.start0(Native Method) > at java.lang.Thread.start(Thread.java:597) > at org.apache.hadoop.dfs.DataNode$DataXceiveServer.run(DataNode.java:906) > at java.lang.Thread.run(Thread.java:619) > {noformat} > Datanode was still running but not much activity besides verification. > Jstack showed no DataXceiveServer running. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.