hadoop-mapreduce-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daryn Sharp (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MAPREDUCE-3825) Need generalized multi-token filesystem support
Date Wed, 08 Feb 2012 20:50:59 GMT

    [ https://issues.apache.org/jira/browse/MAPREDUCE-3825?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13203972#comment-13203972

Daryn Sharp commented on MAPREDUCE-3825:

bq. Good question. If this method is declared in FileSystem then ViewFileSystem has to implement
it and it cannot return single token - it has multiple tokens. The fact that you will never
ever call getDelegationToken on viewFileSystem and always call getEmbeddedFileSystems() does
not matter - ViewFileSystem has to honor the contract for FileSystem since it extends it.

I'd suggest the distinct is that {{getDelegationToken}} requests a token specifically for
that filesystem.  {{ViewFileSystem}} has no intrinsic tokens so it honors the fs contract
by returning null just like any other filesystem with no tokens.  OTOH, {{getDelegationTokens}}
requests all tokens used by that filesystem, which in turn calls {{getDelegationToken}} on
the actual leaf filesystems.  Those leafs either return null or their token.
> 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
>         Attachments: MAPREDUCE-3825.patch
> 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


View raw message