[
https://issues.apache.org/jira/browse/HADOOP-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490242#comment-14490242
]
Nate Edel commented on HADOOP-11824:
------------------------------------
I did not see that, and it does indeed look like this is either a duplicate or
at least covers a case already being considered there. Thanks for bringing it
to my attention! [~eclark] asked me to look into this and I created this to
track the issue; I'll read up on that one thoroughly before proceeding with
anything on this.
> HDFS client and YARN should check for elected master with Zookeeper
> -------------------------------------------------------------------
>
> Key: HADOOP-11824
> URL: https://issues.apache.org/jira/browse/HADOOP-11824
> Project: Hadoop Common
> Issue Type: Improvement
> Reporter: Nate Edel
> Assignee: Nate Edel
>
> When trying to connect to a NameNode (DFS) or Resource Manager (Yarn),
> clients will try multiple connections in order to find the elected master
> node. Clients should instead check the relevant znode in zookeeper.
> This will be especially valuable in DFS after HDFS-6440 is adopted, as the
> worst case scenario in the DFS client will then be testing more than one
> standby nodes in order before finding the master.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
