[
https://issues.apache.org/jira/browse/HDFS-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460187#comment-13460187
]
Hadoop QA commented on HDFS-3918:
---------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12545992/hdfs-3918.txt
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 does not introduce any 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 failed these unit tests in
hadoop-hdfs-project/hadoop-hdfs:
org.apache.hadoop.hdfs.TestDatanodeBlockScanner
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HDFS-Build/3222//testReport/
Console output: https://builds.apache.org/job/PreCommit-HDFS-Build/3222//console
This message is automatically generated.
> EditLogTailer shouldn't log WARN when other node is in standby mode
> -------------------------------------------------------------------
>
> Key: HDFS-3918
> URL: https://issues.apache.org/jira/browse/HDFS-3918
> Project: Hadoop HDFS
> Issue Type: Improvement
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Attachments: hdfs-3918.txt
>
>
> If both nodes are in standby mode, each will be trying to roll the others'
> logs, which results in errors like:
> Unable to trigger a roll of the active NN
> org.apache.hadoop.ipc.StandbyException: Operation category JOURNAL is not
> supported in state standby
> We should catch this specific exception and not log it at WARN level, since
> it's expected behavior.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
