[
https://issues.apache.org/jira/browse/HADOOP-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14070349#comment-14070349
]
Hudson commented on HADOOP-10755:
---------------------------------
SUCCESS: Integrated in Hadoop-Mapreduce-trunk #1839 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1839/])
HADOOP-10755. Support negative caching of user-group mapping. Contributed by
Lei Xu. (wang:
http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1612408)
* /hadoop/common/trunk/hadoop-common-project/hadoop-common/CHANGES.txt
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/fs/CommonConfigurationKeysPublic.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/Groups.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/LdapGroupsMapping.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/ShellBasedUnixGroupsMapping.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/util/Timer.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/main/resources/core-default.xml
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestGroupsCaching.java
*
/hadoop/common/trunk/hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/util/FakeTimer.java
> Support negative caching of user-group mapping
> ----------------------------------------------
>
> Key: HADOOP-10755
> URL: https://issues.apache.org/jira/browse/HADOOP-10755
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.2.0
> Reporter: Andrew Wang
> Assignee: Lei (Eddy) Xu
> Fix For: 2.6.0
>
> Attachments: HADOOP-10755.000.patch, HADOOP-10755.001.patch,
> HADOOP-10755.002.patch, HADOOP-10755.003.patch, HADOOP-10755.004.patch,
> HDFS-5369.000.patch
>
>
> We've seen a situation at a couple of our customers where interactions from
> an unknown user leads to a high-rate of group mapping calls. In one case,
> this was happening at a rate of 450 calls per second with the shell-based
> group mapping, enough to severely impact overall namenode performance and
> also leading to large amounts of log spam (prints a stack trace each time).
> Let's consider negative caching of group mapping, as well as quashing the
> rate of this log message.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
