[
https://issues.apache.org/jira/browse/MAPREDUCE-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mahadev konar updated MAPREDUCE-3380:
-------------------------------------
Attachment: MAPREDUCE-3380_v1.patch
This a very preliminary patch. Lot of issues still need to be addressed. The
patch currently just gets an application delegation token from RM. More work
needs to be done to add the tokens by default to the client credentials when
getdelegationtoken is called. Also, similar RPC needs to be added to jobhistory
for the job history server to be a able to grant application delegation tokens.
Lot more testing needs to be done and also will add tests.
> Token infrastructure for running clients which are not kerberos authenticated
> -----------------------------------------------------------------------------
>
> Key: MAPREDUCE-3380
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3380
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: mr-am, mrv2
> Affects Versions: 0.23.0
> Reporter: Alejandro Abdelnur
> Assignee: Mahadev konar
> Priority: Blocker
> Fix For: 0.23.1
>
> Attachments: MAPREDUCE-3380.branch-0.23.patch,
> MAPREDUCE-3380.branch-0.23.patch, MAPREDUCE-3380_v1.patch
>
>
> The JobClient.getDelegationToken() method is returning NULL, this makes Oozie
> fail when trying to get the delegation token to use it for starting a job.
> What is seems to be happing is that Jobclient.getDelegationToken() calls
> Cluster.getDelegationToken() that calls YarnRunner.getDelegationToken() that
> calls ResourceMgrDelegate.getDelegationToken(). And the last one is not
> implemented. (Thanks Ahmed for tracing this in MR2 code)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
