[ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13704925#comment-13704925 ]
Steve Loughran commented on YARN-913: ------------------------------------- You can list running apps today, but # anyone can start >1 app with the same name # The AM can only register a URL for the AM, and its own RPC service -not any other RPC ports opened, web pages served, etc. At the very least, I'd like to be able to launch an AM with a given app-type & app-name and be confident that no other YARN application with the same (type, name) was running or being started in my name. With the guarantee of a unique (user, type, name) I could use the RM as a bit of a service registry, albeit one limited in what it can register. > 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 > > 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 is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira