[
https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15193769#comment-15193769
]
Robert Joseph Evans commented on YARN-4757:
-------------------------------------------
[~aw], I am not expert on DNS so it is good to hear that you have thought
through this and done your homework. I read up a little on SRV records and it
looks like a good fit. It still does not change the need for 2 way
authentication and making sure that we can restrict who registers for a
service, but because SRV records are not a drop in replacement for A/CNAME
records it should not be as big of an issue.
Clients are likely going to need to make changes to support SRV records, and
from what I can tell java does not come with built in support, not the end of
the world, but also likely non-trivial. Especially when it looks like the
industry has not decided on how they want to support http. (Although I could be
wrong on all of that, because like I said I am not an expert here)
I just want to be sure that you are thinking things through, and it looks like
you are so I am happy.
> [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)
