[
https://issues.apache.org/jira/browse/MAPREDUCE-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12849406#action_12849406
]
Owen O'Malley commented on MAPREDUCE-1624:
------------------------------------------
I'd change the first paragraph to read slightly different:
+ <p>In a secure cluster, the user is authenticated via Kerberos'
+ kinit command. Because of scalability concerns, we don't push
+ the client's Kerberos' tickets in MapReduce jobs. Instead, we
+ acquire delegation tokens from each HDFS NameNode that the job
+ will use and store them in the job as part of job submission.
+ The delegation tokens are automatically obtained
+ for the HDFS that holds the staging directories, where the job
+ job files are written, and any HDFS systems referenced by
+ FileInputFormats, FileOutputFormats, DistCp, and the
+ distributed cache.
+ Other applications require to set the configuration
+ "mapreduce.job.hdfs-servers" for all NameNodes that tasks might
+ need to talk during the job execution. This is a comma separated
+ list of file system names, such as "hdfs://nn1/,hdfs://nn2/".
+ These tokens are passed to the JobTracker
+ as part of the job submission as <a
href="ext:api/org/apache/hadoop/
+ security/credentials">Credentials</a>. </p>
> Document the job credentials and associated details to do with delegation
> tokens (on the client side)
> -----------------------------------------------------------------------------------------------------
>
> Key: MAPREDUCE-1624
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-1624
> Project: Hadoop Map/Reduce
> Issue Type: Improvement
> Components: documentation
> Affects Versions: 0.22.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: job-creds.patch
>
>
> Document the job credentials and associated details to do with delegation
> tokens (on the client side)
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
