You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Chris Nauroth (JIRA)" <ji...@apache.org> on 2015/04/10 21:17:13 UTC

[jira] [Commented] (HADOOP-11824) HDFS client and YARN should check for elected master with Zookeeper

    [ https://issues.apache.org/jira/browse/HADOOP-11824?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14490177#comment-14490177 ] 

Chris Nauroth commented on HADOOP-11824:
----------------------------------------

Hi [~nkedel].  Have you seen HDFS-7858?  Is this issue a duplicate?  I don't recall if there is an equivalent issue filed in YARN for the ResourceManager.

> 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)