[
https://issues.apache.org/jira/browse/HDFS-14528?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16856070#comment-16856070
]
Ayush Saxena commented on HDFS-14528:
-------------------------------------
I thought Observer is a kind of Standby namenode only, as the SBN guyz
proclaimed, with some added functionalities.
So, I personally don't feel observer to be the culprit here. This can be a
common scenario if there are multiple standby namenodes.
To skip the observer because here it happened for observer because observer
doesn't participate in failover(Will it never? Shouldn't be a yes), the
solution sounds more like a workaround to me for the present scenario. It
shouldn't fail technically seems to be a fix to me.
Well if everyone is happy, then No hard feelings.
> [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: Ayush Saxena
> 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]
