[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karthik Kambatla updated YARN-986:
----------------------------------
Description:
Previously: YARN should use cluster-id as token service address
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.
was:
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.
> 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
> Attachments: yarn-986-1.patch, yarn-986-2.patch,
> yarn-986-prelim-0.patch
>
>
> Previously: YARN should use cluster-id as token service address
> 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)
