Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 21292 invoked from network); 14 Jul 2008 22:25:24 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 14 Jul 2008 22:25:24 -0000 Received: (qmail 61669 invoked by uid 500); 14 Jul 2008 22:25:22 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 61649 invoked by uid 500); 14 Jul 2008 22:25:22 -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 61638 invoked by uid 99); 14 Jul 2008 22:25:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Jul 2008 15:25:22 -0700 X-ASF-Spam-Status: No, hits=-1998.4 required=10.0 tests=ALL_TRUSTED,FRT_OFFER2 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; Mon, 14 Jul 2008 22:24:38 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id E1523234C164 for ; Mon, 14 Jul 2008 15:24:31 -0700 (PDT) Message-ID: <424434973.1216074271921.JavaMail.jira@brutus> Date: Mon, 14 Jul 2008 15:24:31 -0700 (PDT) From: "Raghu Angadi (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Commented: (HADOOP-3758) Excessive exceptions in HDFS namenode log file In-Reply-To: <1118303887.1216071391878.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-3758?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613472#action_12613472 ] Raghu Angadi commented on HADOOP-3758: -------------------------------------- Thats pretty painful. We should include "IncorrectVersionException" as one of the fatal exceptions at the datanode. See {{DataNode.java:offserService()}} : {noformat} } catch(RemoteException re) { String reClass = re.getClassName(); if (UnregisteredDatanodeException.class.getName().equals(reClass) || DisallowedDatanodeException.class.getName().equals(reClass)) { LOG.warn("DataNode is shutting down: " + StringUtils.stringifyException(re)); shutdown(); return; } {noformat} > Excessive exceptions in HDFS namenode log file > ---------------------------------------------- > > Key: HADOOP-3758 > URL: https://issues.apache.org/jira/browse/HADOOP-3758 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.17.1 > Reporter: Jim Huang > > I upgraded a big cluster, out of which 10 nodes did not get upgraded. > The namenode log showed excessive exceptions, causing the namenode log to ate the entire partition space, in this case close to 700GB log file was generated on the namenode. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.