hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill de hOra (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HADOOP-3530) Redundant error logging in FSNamesystem.
Date Sun, 03 Aug 2008 09:15:44 GMT

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

Bill de hOra updated HADOOP-3530:

    Attachment: HADOOP-3530-handleCtorExceptions.patch

Patch for review. The patch's policy is to log the IOException and throw the RTE. It's not
pretty, but does deal with the case where an IOException is followed by a Runtime exception.
The question to ask is, is it worth it?

> 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
>         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.

View raw message