[
https://issues.apache.org/jira/browse/HDFS-2665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siddharth Seth updated HDFS-2665:
---------------------------------
Target Version/s: 0.23.1
Status: Open (was: Patch Available)
Not sure why the patch cannot be applied.
test-patch results from applying it locally to trunk.
-1 overall.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 6 new or modified tests.
-1 javadoc. The javadoc tool appears to have generated 26 warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 eclipse:eclipse. The patch built with eclipse:eclipse.
-1 findbugs. The patch appears to introduce 13 new Findbugs (version
1.3.9) warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
The Findbugs warnings are pre-existing ones. Checking about the javadoc
warnings.
The patch does contain changes to common. Should that be a separate jira ?
Re-uploading the same patch again.
> Viewfs changes for MAPREDUCE-3529
> ---------------------------------
>
> Key: HDFS-2665
> URL: https://issues.apache.org/jira/browse/HDFS-2665
> Project: Hadoop HDFS
> Issue Type: Bug
> Affects Versions: 0.23.0
> Reporter: Siddharth Seth
> Priority: Critical
> Attachments: HDFS2665_v1.txt, HDFS2665_v1.txt
>
>
> ViewFs.getDelegationTokens returns a list of tokens for the associated
> namenodes. Credentials serializes these tokens using the service name for the
> actual namenodes. Effectively, tokens are not cached for viewfs (some more
> details in MR 3529). Affects any job which uses the TokenCache in tasks along
> with viewfs (some Pig jobs).
> Talk to Jitendra about this, some options
> 1. Change Credentials.getAllTokens to return the key, instead of just a token
> list (associate the viewfs canonical name with a token in credentials)
> 2. Have viewfs issue a fake token.
> Both of these would allow for a single viewfs configuration only.
> 3. An additional API in FileSystem - something like
> getDelegationTokens(String renewer, Credentials credentials) - which would
> check the credentials object before making token requests to the actual
> namenode.
> 4. An additional API in FileSystem - getCanonicalServiceNames - similar to
> getDelegationTokens, which would return service names for the actual
> namenodes. TokenCache/Credentials can work using this list.
> 5. have getDelegationTokens check the current UGI - and fetch tokens only if
> they don't exist.
> Have a quick patch for 3, along with associated MR changes.
--
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
