hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karthik Kambatla (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (YARN-986) YARN should use cluster-id as token service address
Date Sun, 23 Feb 2014 05:18:20 GMT

     [ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Karthik Kambatla updated YARN-986:
----------------------------------

    Attachment: yarn-986-1.patch

Uploading a patch that works. I am able to run Oozie jobs successfully on a secure cluster
with the patch applied.

Basic approach - instead of using one RM's address in the RMDTToken's service, add both RM's
addresses in the same service. Alternatively, we could generate two tokens as HDFS does, but
a single token with an augment service name seems a simpler approach.

Compatibility - the token service will have two RMs only when HA is enabled. So, on a non-HA
cluster, this is no different from how things work currently. 

> 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-prelim-0.patch
>
>
> 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)

Mime
View raw message