[
https://issues.apache.org/jira/browse/HADOOP-8088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13237215#comment-13237215
]
Hadoop QA commented on HADOOP-8088:
-----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12518767/hadoop-8088-trunk.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
-1 patch. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HADOOP-Build/760//console
This message is automatically generated.
> User-group mapping cache incorrectly does negative caching on transient
> failures
> --------------------------------------------------------------------------------
>
> Key: HADOOP-8088
> URL: https://issues.apache.org/jira/browse/HADOOP-8088
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.20.205.0, 1.0.0, 1.1.0, 0.23.1, 0.24.0
> Reporter: Kihwal Lee
> Fix For: 1.0.2, 0.23.2, 0.24.0
>
> Attachments: hadoop-8088-branch-1.patch, hadoop-8088-branch-1.patch,
> hadoop-8088-trunk.patch, hadoop-8088-trunk.patch, hadoop-8088-trunk.patch
>
>
> We've seen a case where some getGroups() calls fail when the ldap server or
> the network is having transient failures. Looking at the code, the
> shell-based and the JNI-based implementations swallow exceptions and return
> an empty or partial list. The caller, Groups#getGroups() adds this likely
> empty list into the mapping cache for the user. This will function as
> negative caching until the cache expires. I don't think we want negative
> caching here, but even if we do, it should be intelligent enough to
> distinguish transient failures from ENOENT. The log message in the jni-based
> impl also needs an improvement. It should print what exception it encountered
> instead of just saying one happened.
--
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
