[
https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Advertising
Steve Loughran updated YARN-913:
--------------------------------
Attachment: YARN-913-001.patch
YARN 913 registry, patch 001
Features
# ZK based registry YARN service running in the RM. It is currently optional as
to whether this is enabled
# yarn service for clients to use & register
# mini ZK service for use in tests —and an optional feature of any
MiniYarnCluster (credit to Twill team here)
Not implemented
# cleanup policies (after container exit, app attempt, app exit)
# full security (The RM-based service creates the user dir, but the policies
need to be set up to give the user write access under that —and nobody else)
> 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,
> RegistrationServiceDetails.txt, YARN-913-001.patch
>
>
> 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)
