You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Sandeep (JIRA)" <ji...@apache.org> on 2016/09/10 04:38:27 UTC
[jira] [Commented] (HDFS-3714) Disallow manual failover to already
active NN when auto failover is enabled
[ https://issues.apache.org/jira/browse/HDFS-3714?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479135#comment-15479135 ]
Sandeep commented on HDFS-3714:
-------------------------------
Can I takeover this defect ? Couldn't find how to assign it to myself.
> 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
> Labels: newbie
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org