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

Posted to common-dev@hadoop.apache.org by "Tsz Wo (Nicholas), SZE (JIRA)" <ji...@apache.org> on 2008/08/04 19:30:44 UTC

[jira] Assigned: (HADOOP-3530) Redundant error logging in FSNamesystem.

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

Tsz Wo (Nicholas), SZE reassigned HADOOP-3530:
----------------------------------------------

    Assignee: Bill de hOra  (was: Tsz Wo (Nicholas), SZE)

Bill, thanks for working on this.  Assigning it to you.

> 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: Bill de hOra
>            Priority: Critical
>             Fix For: 0.19.0
>
>         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 is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.