You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-dev@hadoop.apache.org by "Allen Wittenauer (JIRA)" <ji...@apache.org> on 2014/07/18 07:33:05 UTC

[jira] [Resolved] (HDFS-171) Redundant error logging in FSNamesystem.

     [ https://issues.apache.org/jira/browse/HDFS-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Allen Wittenauer resolved HDFS-171.
-----------------------------------

    Resolution: Incomplete

Closing this as stale.

> Redundant error logging in FSNamesystem.
> ----------------------------------------
>
>                 Key: HDFS-171
>                 URL: https://issues.apache.org/jira/browse/HDFS-171
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: Konstantin Shvachko
>            Assignee: Bill de hOra
>            Priority: Critical
>         Attachments: HADOOP-3530-handleCtorExceptions.patch
>
>
> 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 was sent by Atlassian JIRA
(v6.2#6252)