[ https://issues.apache.org/jira/browse/HADOOP-7967?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13202789#comment-13202789
]
Sanjay Radia commented on HADOOP-7967:
--------------------------------------
Look at my comment in MAPREDUCE-3825.
There IS support for multi-token file system (hence we changed from getDelegationToken() to
getDelegationTokenS().
I think this is more of an issue of efficiency (see my example in MAPREDUCE-3825).
> Need generalized multi-token filesystem support
> -----------------------------------------------
>
> Key: HADOOP-7967
> URL: https://issues.apache.org/jira/browse/HADOOP-7967
> Project: Hadoop Common
> Issue Type: Bug
> Components: fs, security
> Affects Versions: 0.24.0, 0.23.1
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HADOOP-7967-2.patch, HADOOP-7967-3.patch, HADOOP-7967-4.patch, HADOOP-7967.patch
>
>
> Multi-token filesystem support and its interactions with the MR {{TokenCache}} is problematic.
The {{TokenCache}} tries to assume it has the knowledge to know if the tokens for a filesystem
are available, which it can't possibly know for multi-token filesystems. Filtered filesystems
are also problematic, such as har on viewfs. When mergeFs is implemented, it too will become
a problem with the current implementation. Currently {{FileSystem}} will leak tokens even
when some tokens are already present.
> The decision for token acquisition, and which tokens, should be pushed all the way down
into the {{FileSystem}} level. The {{TokenCache}} should be ignorant and simply request tokens
from each {{FileSystem}}.
--
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
|