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 "Shilun Fan (Jira)" <ji...@apache.org> on 2024/01/04 07:02:00 UTC
[jira] [Updated] (HDFS-14528) Failover from Active to Standby Failed
[ https://issues.apache.org/jira/browse/HDFS-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shilun Fan updated HDFS-14528:
------------------------------
Target Version/s: 3.4.1 (was: 3.4.0)
> Failover from Active to Standby Failed
> ----------------------------------------
>
> Key: HDFS-14528
> URL: https://issues.apache.org/jira/browse/HDFS-14528
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: ha
> Reporter: Ravuri Sushma sree
> Assignee: Ravuri Sushma sree
> Priority: Major
> Labels: multi-sbnn
> Attachments: HDFS-14528.003.patch, HDFS-14528.004.patch, HDFS-14528.005.patch, HDFS-14528.006.patch, HDFS-14528.007.patch, HDFS-14528.2.Patch, ZKFC_issue.patch
>
>
> *In a cluster with more than one Standby namenode, manual failover throws exception for some cases*
> *When trying to exectue the failover command from active to standby*
> *._/hdfs haadmin -failover nn1 nn2, below Exception is thrown_*
> Operation failed: Call From X-X-X-X/X-X-X-X to Y-Y-Y-Y:nnnn failed on connection exception: java.net.ConnectException: Connection refused
> This is encountered in the following cases :
> Scenario 1 :
> Namenodes - NN1(Active) , NN2(Standby), NN3(Standby)
> When trying to manually failover from NN1 to NN2 if NN3 is down, Exception is thrown
> Scenario 2 :
> Namenodes - NN1(Active) , NN2(Standby), NN3(Standby)
> ZKFC's - ZKFC1, ZKFC2, ZKFC3
> When trying to manually failover using NN1 to NN3 if NN3's ZKFC (ZKFC3) is down, Exception is thrown
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org