[jira] [Commented] (YARN-913) Add a way to register long-lived services in a YARN cluster

["Robert Joseph Evans (JIRA)" <ji...@apache.org>]

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

Robert Joseph Evans commented on YARN-913:
------------------------------------------

I need to write a service registry for another project that has a lot of overlap with this JIRA (multi-tenant storm).  I don't have a lot of time to wait for us to all agree on the details but I would like to put the design and APIs up here for review so that hopefully the work can be mostly reused. 

> Add a way to register long-lived services in a YARN cluster
> -----------------------------------------------------------
>
>                 Key: YARN-913
>                 URL: https://issues.apache.org/jira/browse/YARN-913
>             Project: Hadoop YARN
>          Issue Type: New Feature
>          Components: api
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>            Assignee: Robert Joseph Evans
>
> In a YARN cluster you can't predict where services will come up -or on what ports. The services need to work those things out as they come up and then publish them somewhere.
> Applications need to be able to find the service instance they are to bond to -and not any others in the cluster.
> Some kind of service registry -in the RM, in ZK, could do this. If the RM held the write access to the ZK nodes, it would be more secure than having apps register with ZK themselves.



--
This message was sent by Atlassian JIRA
(v6.1#6144)