You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Colin Patrick McCabe (JIRA)" <ji...@apache.org> on 2012/07/10 07:36:35 UTC
[jira] [Commented] (HDFS-3611) NameNode prints unnecessary WARNs
about edit log normally skipping a few bytes
[ https://issues.apache.org/jira/browse/HDFS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13410061#comment-13410061 ]
Colin Patrick McCabe commented on HDFS-3611:
--------------------------------------------
I guess changing it to an INFO might be appropriate. It's definitely not worth a WARN.
> NameNode prints unnecessary WARNs about edit log normally skipping a few bytes
> ------------------------------------------------------------------------------
>
> Key: HDFS-3611
> URL: https://issues.apache.org/jira/browse/HDFS-3611
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: name-node
> Affects Versions: 2.0.0-alpha
> Reporter: Harsh J
> Priority: Trivial
> Labels: newbie
>
> The NameNode currently warns these form of lines at every startup, even if there's no trouble really. For instance, the below is from a NN startup that was only just freshly formatted.
> {code}
> 12/07/08 20:00:22 WARN namenode.EditLogInputStream: skipping 1048563 bytes at the end of edit log '/Users/harshchouraria/Work/installs/temp-space/tmp-default/dfs-cdh4/data/current/edits_0000000000000000003-0000000000000000003': reached txid 3 out of 3
> {code}
> If this skipping is not really a cause for warning, we should not log it at a WARN level but at an INFO or even DEBUG one. Avoids users getting unnecessarily concerned.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira