[
https://issues.apache.org/jira/browse/HADOOP-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783455#comment-13783455
]
Sanjay Radia commented on HADOOP-10012:
---------------------------------------
Turns out the key name in the map is not used to lookup a token when connecting
to a service. Instead the token selector grabs all tokens and uses the service
name *inside* the token:
{code}
for (Token<? extends TokenIdentifier> token : tokens) {
if (kindName.equals(token.getKind())
&& service.equals(token.getService())) {
return (Token<TokenIdent>) token;
}
}
{code}
I think changing the key in the map should be okay.
Daryn added this for debugging assistance - quote from IM:
{quote}
I figured it should have a unique name just in case, for some reason, the
client really did have a token for the physical service. Plus to simplify
debugging if something goes awry again.
it won't break anything, because nothing really looks for a token by its key
other than some mr/yarn stuff (grumble)
{quote}
+1 for the patch.
Todd/Atm - didn't you run into this bug with CDH4 and CDH5 (even though CDH
ships MR1, wouldn't it run into the same issue?)
> Secure Oozie jobs fail with delegation token renewal exception in HA setup
> --------------------------------------------------------------------------
>
> Key: HADOOP-10012
> URL: https://issues.apache.org/jira/browse/HADOOP-10012
> Project: Hadoop Common
> Issue Type: Bug
> Components: ha
> Affects Versions: 2.1.1-beta
> Reporter: Arpit Gupta
> Assignee: Suresh Srinivas
> Attachments: HADOOP-10012.patch
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
