You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Lei (Eddy) Xu (JIRA)" <ji...@apache.org> on 2014/06/26 19:09:25 UTC

[jira] [Moved] (HADOOP-10755) Support negative caching of user-group mapping

     [ https://issues.apache.org/jira/browse/HADOOP-10755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lei (Eddy) Xu moved HDFS-5369 to HADOOP-10755:
----------------------------------------------

          Component/s:     (was: namenode)
                       security
    Affects Version/s:     (was: 2.2.0)
                       2.2.0
                  Key: HADOOP-10755  (was: HDFS-5369)
              Project: Hadoop Common  (was: Hadoop HDFS)

> 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
>         Attachments: 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)