Steve Loughran updated YARN-913:
    Attachment: YARN-913-019.patch

This a patch which addresses sanjay's review comments, with the key changes 

* {{ServiceRecord}} supports arbitrary string attributes; the yarn ID and 
persistence are simply two of these.
* moved zk-related classes under {{/impl/zk}} package
* TLA+ spec in sync with new design

I also 
* moved the packaging from {{org.apache.hadoop.yarn.registry}} to  
{{org.apache.hadoop.registry}}. That would reduce the impact of any promotion 
of the registry into hadoop-common if ever desired.
* moved the registry/site documentation under yarn-site and hooked up with 
existing site docs.
* added the TLA toolbox generated artifacts (pdf and a toolbox dir) to 

> 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, YARN-913-002.patch, YARN-913-003.patch, 
> YARN-913-003.patch, YARN-913-004.patch, YARN-913-006.patch, 
> YARN-913-007.patch, YARN-913-008.patch, YARN-913-009.patch, 
> YARN-913-010.patch, YARN-913-011.patch, YARN-913-012.patch, 
> YARN-913-013.patch, YARN-913-014.patch, YARN-913-015.patch, 
> YARN-913-016.patch, YARN-913-017.patch, YARN-913-018.patch, 
> YARN-913-019.patch, yarnregistry.pdf, yarnregistry.pdf, 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

Reply via email to