[
https://issues.apache.org/jira/browse/HADOOP-8208?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237966#comment-13237966
]
Hadoop QA commented on HADOOP-8208:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12519873/hadoop-8208.txt
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+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:
org.apache.hadoop.fs.viewfs.TestViewFsTrash
+1 contrib tests. The patch passed contrib unit tests.
Test results:
https://builds.apache.org/job/PreCommit-HADOOP-Build/778//testReport/
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/778//console
This message is automatically generated.
> Disallow self failover
> ----------------------
>
> Key: HADOOP-8208
> URL: https://issues.apache.org/jira/browse/HADOOP-8208
> Project: Hadoop Common
> Issue Type: Bug
> Components: ha
> Reporter: Eli Collins
> Assignee: Eli Collins
> Attachments: hadoop-8208.txt, hdfs-3145.txt
>
>
> It is currently possible for users to make a standby NameNode failover to
> itself and become active. We shouldn't allow this to happen in case operators
> mistype and miss the fact that there are now two active NNs.
> {noformat}
> bash-4.1$ hdfs haadmin -ns ha-nn-uri -failover nn2 nn2
> Failover from nn2 to nn2 successful
> {noformat}
> After the failover above, nn2 will be active.
--
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
