You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Jonathan Maron (JIRA)" <ji...@apache.org> on 2016/03/23 18:36:25 UTC

[jira] [Updated] (YARN-4757) [Umbrella] Simplified discovery of services via DNS mechanisms

     [ https://issues.apache.org/jira/browse/YARN-4757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Maron updated YARN-4757:
---------------------------------
    Attachment: YARN-4757- Simplified discovery of services via DNS mechanisms.pdf

I’ve posted a document providing greater detail concerning this effort.  It is intended as a description of the background, a proposed architectural approach, implementation details, and some open issues.  I've already had some initial reviews that were of great help in both describing existing points and identifying additional ones. /cc [~vvasudev],  [~vinodkv], [~sidharta-s], [~stevel@apache.org], [~elserj]

> [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
>         Attachments: YARN-4757- Simplified discovery of services via DNS mechanisms.pdf
>
>
> [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 end­points 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)