[
https://issues.apache.org/jira/browse/HADOOP-6988?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12918368#action_12918368
]
Aaron T. Myers commented on HADOOP-6988:
----------------------------------------
Allen: I agree with Owen - it doesn't make sense to remove this environment
variable. It is primarily used internally, though its use is documented in
hdfs_user_guide.xml and mapred_tutorial.xml. The interaction between this and
the conf var is that all tokens specified via either method are added to a
single credentials object - nothing's going to take precedence.
Owen: the motivation for this change is not with regard to passing delegation
tokens from job to tasks, but rather with submitting jobs in the first place,
which is another use for HADOOP_TOKEN_FILE_LOCATION. I'd like to be able to
specify multiple tokens (gotten from fetchdt, or via other means) which a job
could use to, for example, authenticate to multiple NNs and JTs. I considered
creating a tool which would be capable of merging multiple delegation token
files into one, but this seemed like a cleaner solution.
Good point on making this comma-separated. I'll definitely do that.
> Add support for reading multiple hadoop delegation token files
> --------------------------------------------------------------
>
> Key: HADOOP-6988
> URL: https://issues.apache.org/jira/browse/HADOOP-6988
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 0.22.0
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
>
> It would be nice if there were a way to specify multiple delegation token
> files via the HADOOP_TOKEN_FILE_LOCATION environment variable and the
> "mapreduce.job.credentials.binary" configuration value. I suggest a
> colon-separated list of paths, each of which is read as a separate delegation
> token file.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
