[
https://issues.apache.org/jira/browse/HDFS-13312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621015#comment-16621015
]
Íñigo Goiri commented on HDFS-13312:
------------------------------------
As I'm working on running Hadoop on VMs, I see more and more the need to have a
framework to discover servers.
I played with DNS but this works for fixed setups but it's not very elastic
(I'm limited to having always say 3 NNs).
I'll open a JIRA in commons to define the framework and use it as the branch
for working on this.
As there are subparts in both HDFS and YARN this won't be a pure umbrella; I
hope linking JIRAs and merging into the branch is fine.
Anyway, I'll link the JIRA once I open it here and we can start the discussion
there.
> 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
> Attachments: HDFS-13312.000.patch, HDFS-13312.001.patch,
> HDFS-13312.002.patch, HDFS-13312.003.patch
>
>
> 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]
