[
https://issues.apache.org/jira/browse/MAPREDUCE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202762#comment-13202762
]
Sanjay Radia commented on MAPREDUCE-3825:
-----------------------------------------
The general idea is that that when a job is submitted one has a list of paths
(input, output, defaultfs, etc). From that list of paths one gets a set of file
systems, eliminates duplicates and then get delegation tokens for each.
This works except that it may not be efficient in some cases. Eg:
* Input path is hdfs://foo/bar
* default fs is viewfs:/// which has mounted hdfs://foo/
In this case one will obtain the delegation tokens for hdfs://foo *twice*.
The Jira description seems to suggest that the current implementation does not
work (Bug/Major) while what i am concluding is that it is not optimal.
> Need generalized multi-token filesystem support
> -----------------------------------------------
>
> Key: MAPREDUCE-3825
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-3825
> Project: Hadoop Map/Reduce
> Issue Type: Bug
> Components: security
> Affects Versions: 0.23.1, 0.24.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
>
> This is the counterpart to HADOOP-7967. The token cache currently tries to
> assume a filesystem's token service key. The assumption generally worked
> while there was a one to one mapping of filesystem to token. With the advent
> of multi-token filesystems like viewfs, the token cache will try to use a
> service key (ie. for viewfs) that will never exist (because it really gets
> the mounted fs tokens).
--
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
