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

["Steve Loughran (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

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

Updated patch
# comments & renames the {{HOSTNAME_PATTERN}} field (for AW)
# registryOperationsStatus record holds the shortname of the stat'd record, not the full path (for Sanjay)
# moves the {{listFull}} operation to list then stat the children out of the core {{RegistryOperations}} API and into {{RegistryUtils}}, as it is a utility action built from the lower level operations. Migration to this across the codebase.
# made that stat operation robust against child entries being deleted during the action
# same for the registry purge: there may be race conditions of overlapping delete operations ... this is not an error

> 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, 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)