[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13897542#comment-13897542
]
Vinod Kumar Vavilapalli commented on YARN-986:
----------------------------------------------
[~daryn],
bq. This sounds like NN HA tokens which IMHO are rather hacky. I've been
intending to take advantage of my RPCv9 auth changes for the server to tell the
client the token service (or perhaps another field) it needs to decouple tokens
entirely from IP/hostname. Thoughts on this approach?
Do we know of an ETA of when you are making those changes? If they aren't
within a month, in the interest of progress, we are going to go ahead with NN
HA like approach here. Once that is in place, both NN as well as RM can be
modified to use the RPC layer features and get rid of this stuff.
> 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
> Priority: Blocker
>
> 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)
