[
https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193930#comment-15193930
]
Allen Wittenauer commented on YARN-4757:
----------------------------------------
bq. I am not expert on DNS so it is good to hear that you have thought through
this and done your homework.
I'm (probably) not doing the work either, but I've been working with DNS for an
extremely long time... (as in "before Java existed" long time)
bq. It still does not change the need for 2 way authentication and making sure
that we can restrict who registers for a service
Yup. I share this concern. This is a security hole waiting to happen.
bq. I can tell java does not come with built in support, not the end of the
world, but also likely non-trivial.
I'm assuming by built-in, you mean a specific method for querying SRV records
since the Java libs clearly allow one to query for records, even if it is
through things like the "fun" JNDI. But fret not, others are already working
in this space with lots of example code to look at. See
https://github.com/spotify/dns-java,
https://github.com/couchbase/couchbase-java-client, http://www.dnsjava.org/,
and several others. This isn't new ground being covered here at all and all of
the above referenced code should be in a compatible license.
> [Umbrella] Simplified discovery of services via DNS mechanisms
> --------------------------------------------------------------
>
> Key: YARN-4757
> URL: https://issues.apache.org/jira/browse/YARN-4757
> Project: Hadoop YARN
> Issue Type: New Feature
> Reporter: Vinod Kumar Vavilapalli
> Assignee: Jonathan Maron
>
> [See overview doc at YARN-4692, copying the sub-section (3.2.10.2) to track
> all related efforts.]
> In addition to completing the present story of service-registry (YARN-913),
> we also need to simplify the access to the registry entries. The existing
> read mechanisms of the YARN Service Registry are currently limited to a
> registry specific (java) API and a REST interface. In practice, this makes it
> very difficult for wiring up existing clients and services. For e.g, dynamic
> configuration of dependent endpoints of a service is not easy to implement
> using the present registry-read mechanisms, *without* code-changes to
> existing services.
> A good solution to this is to expose the registry information through a more
> generic and widely used discovery mechanism: DNS. Service Discovery via DNS
> uses the well-known DNS interfaces to browse the network for services.
> YARN-913 in fact talked about such a DNS based mechanism but left it as a
> future task. (Task) Having the registry information exposed via DNS
> simplifies the life of services.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
