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

Karthik Kambatla commented on YARN-986:
---------------------------------------

IMO, the following approach should address the need: ({{rpc-address}} refers to 
each of {{address}}, {{scheduler.address}}, {{admin.address}}, 
{{resource-tracker.address}}, {{webapp.address}})

# {{yarn.resourcemanager.clusterid}} gives the clusterid/logical name (e.g. 
foo), and the actual RPC addresses for the cluster are to be specified as 
{{yarn.resourcemanager.<rpc-address>.foo}}
# Helper class {{ConfigurationUtil}} adds variants of getClusterId(), get/set 
(<rpc-address>, clusterid) methods.
# RM uses the above helper methods to set all the rpc-addresses during init for 
the servers to use. If no cluster-id, the <rpc-addresses> are used as is, so 
current configurations continue to work as expected.
# The individual RPC services remain unchanged.
# Clients can direct their queries to a particular cluster by setting either 
the cluserid, or <rpc-address>.
# This trivially extends to HA clusters - the RPC addresses become 
{{yarn.resourcemanager.<rpc-address>.clusterid.instanceid}}

Thoughts? 
                
> YARN should have a ClusterId/ServiceId
> --------------------------------------
>
>                 Key: YARN-986
>                 URL: https://issues.apache.org/jira/browse/YARN-986
>             Project: Hadoop YARN
>          Issue Type: Sub-task
>            Reporter: Vinod Kumar Vavilapalli
>            Assignee: Karthik Kambatla
>
> This needs to be done to support non-ip based fail over of RM. Once the 
> server sets the token service address to be this generic ClusterId/ServiceId, 
> clients can translate it to appropriate final IP and then be able to select 
> tokens via TokenSelectors.
> Some workarounds for other related issues were put in place at YARN-945.

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

Reply via email to