[
https://issues.apache.org/jira/browse/YARN-986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13919685#comment-13919685
]
Vinod Kumar Vavilapalli commented on YARN-986:
----------------------------------------------
Thanks Karthik, the latest patch looks good. I wish there were more tests
directly validating tokens across fail-over. In the interest of progress, I am
fine for now with your manual testing, we can file a separate ticket for that.
The test failures are unrelated, commented on HDFS-6040. But I am not sure
there are any test or other issues with our patch itself. Let's see how
HDFS-6040 goes. Or we can run the jenkins script with tests offline.
> 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
(v6.2#6252)
