hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-913) Umbrella: Add a way to register long-lived services in a YARN cluster
Date Wed, 11 Feb 2015 14:24:13 GMT

    [ https://issues.apache.org/jira/browse/YARN-913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316253#comment-14316253

Hudson commented on YARN-913:

FAILURE: Integrated in Hadoop-trunk-Commit #7069 (See [https://builds.apache.org/job/Hadoop-trunk-Commit/7069/])
YARN-2616 [YARN-913] Add CLI client to the registry to list, view and manipulate entries.
(Akshay Radia via stevel) (stevel: rev 362565cf5a8cbc1e7e66847649c29666d79f6938)
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/test/java/org/apache/hadoop/registry/cli/TestRegistryCli.java
* hadoop-yarn-project/hadoop-yarn/hadoop-yarn-registry/src/main/java/org/apache/hadoop/registry/cli/RegistryCli.java
* hadoop-yarn-project/CHANGES.txt

> Umbrella: 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, YARN-913-020.patch, YARN-913-021.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

View raw message