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] [Commented] (YARN-986) RM DT token service should have service addresses of both RMs
Date Tue, 04 Mar 2014 02:28:23 GMT

    [ https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13918951#comment-13918951

Karthik Kambatla commented on YARN-986:

bq. There are some related TODOs in ClientRMProxy.setupTokens() that we put before. Search
for YARN-986. We can fix them here or separately.
Created YARN-1779 to address AMRMTokens. This JIRA is only for RMDTTokens. 

bq. getRMDelegationTokenService() API: Not sure why we are doing yarnConf.set(YarnConfiguration.RM_HA_ID,
bq. you are only building the service against one address RM_ADDRESS.
Discussed with Vinod offline. YarnConfiguration#getSocketAddr already handles the HA case.
Updated its javadoc to reflect that. 

Addressed other comments. Again, verified manually running Oozie jobs. 

> RM DT token service should have service addresses of both RMs
> -------------------------------------------------------------
>                 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-3.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

View raw message