[
https://issues.apache.org/jira/browse/HADOOP-3530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12604333#action_12604333
]
Tsz Wo (Nicholas), SZE commented on HADOOP-3530:
------------------------------------------------
> I was in fact talking about the following new line in the code ...
The situation here is similar: initialize(nn, conf) may throw an exception and
then close() may throw a second exception. If we get ride of LOG.error(...),
the first exception (usually, the most important exception) won't be logged.
> 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.
