[
https://issues.apache.org/jira/browse/HDFS-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856050#comment-16856050
]
Ayush Saxena commented on HDFS-14528:
-------------------------------------
Thanx everyone for the discussion, Trying to understand the issue?
{quote}Looks ObserverZKFC might be down.
{quote}
Is the failure since the namenode ZKFC was down? Nothing to do it being an
observer?
bq. So,Current fix should be fine where we are skipping observer
Can this not occur for standby namenodes too, if there are multiple standby
namenodes, one standby namenode ZKFC is down? Would this not occur, will it
occur only if it is observer?
> [SBN Read]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
> Attachments: ZKFC_issue.patch
>
>
> *Started an HA Cluster with three nodes [ _Active ,Standby ,Observer_ ]*
> *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; For more
> details see: [http://wiki.apache.org/hadoop/ConnectionRefused]
> at sun.reflect.GeneratedConstructorAccessor7.newInstance(Unknown Source)
> at
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
> at org.apache.hadoop.net.NetUtils.wrapWithMessage(NetUtils.java:831)
> at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:755)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
