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

Sanjay Radia commented on MAPREDUCE-3825:
-----------------------------------------

Let me correct my previous comment where i hit the add button accidentally.
* TokenCache is an internal impl and can be changed to work correctly with the 
existing API. For example "TokenCache thinks the viewfs authority is a service 
name so it tries to resolve it as a hostname:port tuple and fails." is the a 
problem with TokenCache.
** hostname-port was never a guarantee of FS URIs and so if tokenCache made 
that assumption it was a mistake. 
** hostname-port is needed for the renewal and is encoded in the token - hence 
this should not be an issue.
** One issue is that tokenCache maps a fs-uri to a token when it could have 
mapped to set of tokens.
* Viewfilesysgtem can be fixed to ignore duplicate mounts and tokens. 

Both you and I have given examples of cases where duplicate tokens will be 
added; duplicate tokens is an inefficiency.

Lets change code/interfaces to deal with the inefficiency. However your 
conclusion that there isn't multi-token support or that this is major-bug are 
incorrect.

To start with I would like to change the jira to "improvement"  and change the 
title to "Improve token management to eliminate duplicate tokens"


                
> 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

        

Reply via email to