[
https://issues.apache.org/jira/browse/HDFS-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421135#comment-13421135
]
Eli Collins commented on HDFS-3714:
-----------------------------------
Thanks to Stephen Chu for identifying this bug.
> Disallow manual failover to already active NN when auto failover is enabled
> ---------------------------------------------------------------------------
>
> Key: HDFS-3714
> URL: https://issues.apache.org/jira/browse/HDFS-3714
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: auto-failover
> Affects Versions: 2.0.0-alpha
> Reporter: Eli Collins
> Priority: Minor
>
> If nn1 is active and nn2 is standby "hdfs haadmin -failover nn2 nn1" says
> that failover to nn1 is successful even though nn1 is already active. When
> only manual failover is active, there is a check that tells users that the
> user can't failover to an already active service. We should have the same
> check for auto failover.
> {noformat}
> bash-4.1$ hdfs haadmin -failover nn2 nn1
> Failover to NameNode at brut01.sf.cloudera.com/172.22.35.149:17020 successful
> bash-4.1$ hdfs haadmin -failover nn2 nn1
> Failover to NameNode at brut01.sf.cloudera.com/172.22.35.149:17020 successful
> bash-4.1$ hdfs haadmin -failover nn2 nn1
> Failover to NameNode at brut01.sf.cloudera.com/172.22.35.149:17020 successful
> {noformat}
--
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
