[
https://issues.apache.org/jira/browse/HDFS-3611?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13411193#comment-13411193
]
Hadoop QA commented on HDFS-3611:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12535963/HDFS-3611.001.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 2 new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed unit tests in
hadoop-hdfs-project/hadoop-hdfs.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/2784//testReport/
Findbugs warnings:
https://builds.apache.org/job/PreCommit-HDFS-Build/2784//artifact/trunk/patchprocess/newPatchFindbugsWarningshadoop-hdfs.html
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/2784//console
This message is automatically generated.
> 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
> Attachments: 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
