hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Harsh J (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3611) NameNode prints unnecessary WARNs about edit log normally skipping a few bytes
Date Wed, 11 Jul 2012 03:39:34 GMT

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

Harsh J updated HDFS-3611:

          Resolution: Fixed
       Fix Version/s: 2.0.1-alpha
    Target Version/s:   (was: 2.0.1-alpha)
              Status: Resolved  (was: Patch Available)

Committed to branch-2 and trunk. Thanks for improving this and contributing Colin!
> 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
>            Assignee: Colin Patrick McCabe
>            Priority: Trivial
>              Labels: newbie
>             Fix For: 2.0.1-alpha
>         Attachments: HDFS-3611.001.patch, HDFS-3611.001.patch
> 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


View raw message