[
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-002.patch
Patch -002
# adds persistence policy
# {{RegistryOperationsService}} implements callbacks for various RM events, and
implements the setup/purge behaviour underneath.
# adds a new class in the resource manager, {{RegistryService}}. This bridges
from YARN to the registry by subscribing to application and container events,
translating and forwarding to the {{RegistryOperationsService}} where they may
trigger setup/purge operations
# Hooks this up to the RM
# Extends the DistributedShell by enabling it to register service records with
the different persistence options.
# Adds a test to verify the distributed shell does register the entries, and
that the purgeable ones are purged after the application completes.
This means the {{TestDistributedShell}} test is now capable of verifying that
YARN applications can register themselves, that they can then be discovered,
and that the RM cleans up after they terminate.
> 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, 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)
