[
https://issues.apache.org/jira/browse/HDFS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16408818#comment-16408818
]
Íñigo Goiri commented on HDFS-13312:
------------------------------------
In HDFS-13098, we would like to support the Datanodes contacting the Routers to
discover the NNs instead of explicitly setting up the nameservice.
I think that the discovery described in this JIRA may target the clients and
not the workers (i.e., DNs).
In any case, I think adding this support is valuable and HDFS-13098 could
leverage it too (similar for YARN).
Can you point to the solution to do RM HA discovery?
> NameNode High Availability ZooKeeper based discovery rather than explicit
> nn1,nn2 configs
> -----------------------------------------------------------------------------------------
>
> Key: HDFS-13312
> URL: https://issues.apache.org/jira/browse/HDFS-13312
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha, hdfs, namenode, nn
> Affects Versions: 2.9.1
> Reporter: Hari Sekhon
> Priority: Major
>
> Improvement Request for HDFS NameNode HA to use ZooKeeper based dynamic
> discovery rather than explicitly setting the NameNode addresses via nn1,n2 in
> the configs.
> One proprietary Hadoop vendor already uses ZK for Resource Manager HA
> discovery - it makes sense that the open source core should do this for both
> Yarn and HDFS.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
