hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Weise (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-913) Add a way to register long-lived services in a YARN cluster
Date Fri, 12 Jul 2013 23:33:48 GMT

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

Thomas Weise commented on YARN-913:
-----------------------------------

ZK backed registry looks like a good implementation option. Instead of application specific
flavors of service registry implementations through ZK, it would be great to have a reusable
implementation as part of YARN. For publishing services to other applications, but also within
an application. For example, containers may need to find the AM after recovery (assuming that
containers remain active while the AM goes down and is recovered). 

Encapsulating such registry in the RM would provide for a single point of configuration and
secure write access (and pluggable implementation).
                
> 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
>    Affects Versions: 3.0.0
>            Reporter: Steve Loughran
>
> 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 is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message