[
https://issues.apache.org/jira/browse/HADOOP-10012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783294#comment-13783294
]
Vinod Kumar Vavilapalli commented on HADOOP-10012:
--------------------------------------------------
Tx for filing this Arpit. I'd like to also credit [~venkatnrangan] for his
extensive debugging to figure out the underlying issue.
What's happening here is that
- In the oozie's launcher job, before we create a job-client, Cluster.java
creates a file-system object which eventually invokes DFS HAUtils code that
clones the single delegation token with logical URI as service-name into
multiple tokens with the ip-addresses
- Once the UGI is 'polluted' with these duplicate tokens, JobClient uses the
tokens from UGI to submit to RM which eventually fails to renew these 'fake'
tokens as it cannot reach the stand-by NN for renewal
- The failure to renew tokens fails the job.
> Secure Oozie jobs 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
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
