[
https://issues.apache.org/jira/browse/MAPREDUCE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203182#comment-13203182
]
Sanjay Radia commented on MAPREDUCE-3825:
-----------------------------------------
Here are two possible solutions
# Two APIs
** tokens[] FileSystem#getDelegationTokens(string renewer);
** URI[] FileSystems#getEmbeddedFileSystems();
With this approach the caller calls getEmbeddedFileSystems across MR input, MR
output and default and other fileSystems and eliminates the duplicate file
systems. (Note ViewFs will eliminate duplicates before returning the set of
file systems).
At end call getDelegationTokens(renewer) for each of non-dulicate URIs;
getDelegationTokens will return only one token since it is guaranteed that the
calls are for the leaf file systems.
# One API
** void FileSystem#addDelegationTokens(renewer, credentials) //adds tokens to
credentials if not already in.
Go through each of across MR input, MR output and default and
other fileSystems and call addDelegationTokens(renewer, credentials) to add
tokens to the credentials. Duplicates are eliminated by checking service name
(host:port)
> 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
