[
https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13799170#comment-13799170
]
Steve Loughran commented on YARN-913:
-------------------------------------
# your design reminds me a lot of bonjour, just a thought.
# my use case is "ensure that no other instance of my application name exists,
eg {{steve/hoya/cluster4}} , so avoiding race conditions. I'd have the server
attempt to register on startup -and if it could not, fail. Implication: atomic
registration by name
# Hadoop now ships with the ZK JAR, for HA NN, soon the RM will use it too.
This will let us assume that ZK is a live service, and make use of it.
> 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
> Attachments: RegistrationServiceDetails.txt
>
>
> 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)
