[
https://issues.apache.org/jira/browse/HADOOP-6545?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12833682#action_12833682
]
Hadoop QA commented on HADOOP-6545:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12435830/6545-1.patch
against trunk revision 909806.
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified
tests.
Please justify why no new tests are needed for this
patch.
Also please list what manual steps were performed to
verify this patch.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
Test results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/5/testReport/
Findbugs warnings:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/5/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/5/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://hudson.zones.apache.org/hudson/job/Hadoop-Patch-h1.grid.sp2.yahoo.net/5/console
This message is automatically generated.
> Cached FileSystem objects can lead to wrong token being used in setting up
> connections
> --------------------------------------------------------------------------------------
>
> Key: HADOOP-6545
> URL: https://issues.apache.org/jira/browse/HADOOP-6545
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.22.0
> Reporter: Devaraj Das
> Assignee: Devaraj Das
> Fix For: 0.22.0
>
> Attachments: 6545-1.patch
>
>
> The FileSystem class caches the filesystem objects that it creates for users.
> For some cases, e.g., if the filesystem object is actually a
> DistributedFileSystem, it also has an associated RPC client and hence an UGI
> for the respective user. This could lead to issues to do with using the right
> credentials when connecting with the namenode. The credentials in the UGI is
> never updated (even if the user in question now has new credentials) and in
> case the cached UGI's credentials have expired, this would lead to
> authentication error whenever there is a re-authentication (in the process of
> re-establishing connection to the namenode).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
