[
https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Steve Loughran updated YARN-913:
--------------------------------
Attachment: yarnregistry.tla
yarnregistry.pdf
2014-09-08_YARN_Service_Registry.pdf
h3. Updated YARN service registry description
This adds a {{persistence}} field to service records, enabling the records to
be automatically deleted (along with all child entries) when the application,
app attempt or container is terminated.
h3. TLA+ service registry specification.
This is my initial attempt to define the expected behaviour of a service
registry built atop zookeeper. Corrections welcome.
> 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, resourcemanager
> Affects Versions: 2.5.0, 2.4.1
> Reporter: Steve Loughran
> Assignee: Steve Loughran
> Attachments: 2014-09-03_Proposed_YARN_Service_Registry.pdf,
> 2014-09-08_YARN_Service_Registry.pdf, RegistrationServiceDetails.txt,
> YARN-913-001.patch, yarnregistry.pdf, yarnregistry.tla
>
>
> 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.3.4#6332)
