[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13777796#comment-13777796
]
Bikas Saha commented on YARN-986:
---------------------------------
This jira has been repurposed beyond tokens. We need a logical name for the RM
instances so that they can correctly pick their configs and clients can
identify them by name. Something like the namespace id in HDFS.
By the time we come to security and tokens, it would make sense to use the
approach that makes configuring it easy for users.
Can you please provide details of what you were thinking. Our initial idea was
to have the RM instance identify its token with its own logical id. Then the
clients will translate the logical id to the physical id of the instance based
on their configuration.
> 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
