Return-Path: Delivered-To: apmail-hadoop-core-dev-archive@www.apache.org Received: (qmail 87557 invoked from network); 11 Jun 2008 18:49:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 11 Jun 2008 18:49:08 -0000 Received: (qmail 56245 invoked by uid 500); 11 Jun 2008 18:49:09 -0000 Delivered-To: apmail-hadoop-core-dev-archive@hadoop.apache.org Received: (qmail 56219 invoked by uid 500); 11 Jun 2008 18:49:09 -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 56207 invoked by uid 99); 11 Jun 2008 18:49:09 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Jun 2008 11:49: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; Wed, 11 Jun 2008 18:48:27 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 702AF234C135 for ; Wed, 11 Jun 2008 11:48:45 -0700 (PDT) Message-ID: <531541051.1213210125444.JavaMail.jira@brutus> Date: Wed, 11 Jun 2008 11:48:45 -0700 (PDT) From: "Konstantin Shvachko (JIRA)" To: core-dev@hadoop.apache.org Subject: [jira] Updated: (HADOOP-3530) Redundant error logging in FSNamesystem. In-Reply-To: <1271377926.1213148625066.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-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Konstantin Shvachko updated HADOOP-3530: ---------------------------------------- Priority: Critical (was: Blocker) Fix Version/s: (was: 0.18.0) 0.19.0 I agree when initialize() fails and then consequently close() throws a runtime exception we will get 2 dfiferent messages. This is the case when the system cannot neither start nor exit. But if close succeeds doubling the message is confusing. I am looking at the close code in general and it looks like we will need to clean up handling of exceptions in general. So this is not a one line fix, I am reassigning it to 0.19. > Redundant error logging in FSNamesystem. > ---------------------------------------- > > Key: HADOOP-3530 > URL: https://issues.apache.org/jira/browse/HADOOP-3530 > Project: Hadoop Core > Issue Type: Bug > Components: dfs > Affects Versions: 0.18.0 > Reporter: Konstantin Shvachko > Assignee: Tsz Wo (Nicholas), SZE > Priority: Critical > Fix For: 0.19.0 > > > HADOOP-3509 introduced a new error message which is logged if FSNamesystem fails to initialize. > This message turned out to be redundant, because it should and is logged further up the stack say in NameNode.main(). > Right now I see the exception logged twice when I run a stand-alone name-node. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.