[
https://issues.apache.org/jira/browse/MAPREDUCE-1383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12803621#action_12803621
]
Devaraj Das commented on MAPREDUCE-1383:
----------------------------------------
After a quick look at the patch, some comments:
1) The call to populateTokenCache should be done just before the submitJob call
(so that we definitely have all the information to do with namenodes the job
wishes to talk to at runtime, even those that are potentially added within
calls to user's InputFormat.getSplits)
2) The configs mapreduce.job.hdfs-servers and
mapreduce.job.kerberos.jtprinicipal could probably be defined in
JobContext.java.
3) Also, though not directly related to this patch, but could you please move
the JOB_TOKEN_FILE definition from JobContext.java to TokenStorage.java. Ditto
for SecureShuffleUtils.JOB_TOKEN_FILENAME
> Allow storage and caching of delegation token.
> ----------------------------------------------
>
> Key: MAPREDUCE-1383
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1383
> Project: Hadoop Map/Reduce
> Issue Type: New Feature
> Reporter: Boris Shkolnik
> Attachments: MAPREDUCE-1383-1.patch, MAPREDUCE-1383-2.patch
>
>
> Client needs to obtain delegation tokens from all the NameNodes it is going
> to work with and pass it to the application.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
