[
https://issues.apache.org/jira/browse/HADOOP-15774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16621040#comment-16621040
]
Íñigo Goiri commented on HADOOP-15774:
--------------------------------------
This would mainly apply to discoverying:
* Resource Managers
* Namenodes
* Journal nodes
>From the discussion in HDFS-13312, we could have a few implementations:
* Based on local configurations: this would be the first stepping stone and
would just be equivalent to the legacy configuration but going through this
framework.
* Based on ZooKeeper, this may eventually hit scalability issues but it would
be the first distributed setup as most components in Hadoop already use
ZooKeeper.
* Based on Router federation, both YARN and HDFS have Routers that could expose
the locations of the NNs/RMs.
* Some other shared storage (HDFS? HBase?).
I'd like to add some discussion about a DNS setup too.
I've been playing with it and it moves the problem to the maintainer of the DNS
records...
HDFS-13312 already had some discussion; together with the one here, we can put
all into a design doc and start a branch.
[~daryn] anything you want to add to what you mentioned in HDFS-13312?
[~anu] any thoughts on the general approach? I'm not very familiar with the
OZone architecture; do you guys also need to specify servers manually?
> Discovery of HA servers
> -----------------------
>
> Key: HADOOP-15774
> URL: https://issues.apache.org/jira/browse/HADOOP-15774
> Project: Hadoop Common
> Issue Type: New Feature
> Reporter: Íñigo Goiri
> Priority: Major
>
> Currently, Hadoop relies on configuration files to specify the servers.
> This requires maintaining these configuration files and propagating the
> changes.
> Hadoop should have a framework to provide discovery.
> For example, in HDFS, we could define the Namenodes in a shared location and
> the DNs would use the framework to find the Namenodes.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
