hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-7805) NameNode recovery prompt should be printed on console
Date Tue, 17 Feb 2015 22:25:11 GMT

    [ https://issues.apache.org/jira/browse/HDFS-7805?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14325019#comment-14325019
] 

Colin Patrick McCabe commented on HDFS-7805:
--------------------------------------------

Thanks for taking a look at this, [~surendrasingh].  This is a tough JIRA because I do think
it would be nice to have this information in the log file.  But I'm not sure how to get it
there exactly if we use {{System.err.printf}}.  There are also a bunch of other log messages
in recovery mode not affected by your patch, so this isn't a complete solution.

Do you think it's possible to programmatically modify the log4j configuration so that stderr
is one of the targets when recovery mode is enabled?  That seems easier than converting so
many LOG messages to printf, and better for people who want to keep the logs as well.

> NameNode recovery prompt should be printed on console
> -----------------------------------------------------
>
>                 Key: HDFS-7805
>                 URL: https://issues.apache.org/jira/browse/HDFS-7805
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: namenode
>    Affects Versions: 2.6.0
>            Reporter: surendra singh lilhore
>            Assignee: surendra singh lilhore
>         Attachments: HDFS-7805.patch
>
>
> In my cluster root logger is not console, so when I run namenode recovery tool MetaRecoveryContext.java
prompt message is logged in log file.
> Actually is should be display on console.
> Currently it is like this
> {code}
> LOG.info(prompt);
> {code}
> It should be 
> {code}
> System.err.print(prompt);
> {code}
> NameNode recovery prompt should be printed on console



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message