[
https://issues.apache.org/jira/browse/MAPREDUCE-5663?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13870173#comment-13870173
]
Siddharth Seth commented on MAPREDUCE-5663:
-------------------------------------------
bq. if the AM has the corresponding delegation tokens, things work just fine,
Oozie has been doing this for years; the splits are computed in the launcher
job which does not have kerberos credentials.
[~tucu00], My guess is the launcher job is able to compute splits because it
already has access to the tokens. Do you know how Oozie ensures that job
specific tokens are available to the launcher, without calling getSplits etc on
the client node.
The intent of this JIRA is to be able to get the necessary tokens on the client
(based on the Job Configuration), without actually invoking getSplits() and
checkOutputSpecs. The token functionality is currently baked into these methods.
> Add an interface to Input/Ouput Formats to obtain delegation tokens
> -------------------------------------------------------------------
>
> Key: MAPREDUCE-5663
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5663
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Reporter: Siddharth Seth
> Assignee: Michael Weng
> Attachments: MAPREDUCE-5663.4.txt, MAPREDUCE-5663.5.txt,
> MAPREDUCE-5663.6.txt, MAPREDUCE-5663.patch.txt, MAPREDUCE-5663.patch.txt2,
> MAPREDUCE-5663.patch.txt3
>
>
> Currently, delegation tokens are obtained as part of the getSplits /
> checkOutputSpecs calls to the InputFormat / OutputFormat respectively.
> This works as long as the splits are generated on a node with kerberos
> credentials. For split generation elsewhere (AM for example), an explicit
> interface is required.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
