[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13896877#comment-13896877
]
Karthik Kambatla commented on YARN-986:
---------------------------------------
To do this in a backward-compatible way in case users want to use a 2.2.0
client against a 2.4.0 server or vice-versa, I see two approaches:
# Use the cluster-id only for HA cases, and non HA cases continue to use RM
address. This is what HDFS seems to do.
# Use the cluster-id for both HA and non-HA cases, but fallback to use RM
address if need be both on the server and client sides. This can be a little
tricky, but would make it easy to get rid of the RM address parts come
Hadoop-3.0.
[~vinodkv], [~bikassaha] - what do you think?
> YARN should use cluster-id as token service address
> ---------------------------------------------------
>
> 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 was sent by Atlassian JIRA
(v6.1.5#6160)
