hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-13312) NameNode High Availability ZooKeeper based discovery rather than explicit nn1,nn2 configs
Date Mon, 30 Apr 2018 20:35:00 GMT

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

Daryn Sharp commented on HDFS-13312:
------------------------------------

You might want to talk to ZK devs.  An internal dev says ZK will not scale to support this
use case.  I suppose it's pluggable and won't hurt me though...

> 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
>
>
> 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: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org


Mime
View raw message