Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop, mail # dev - 回复: [jira] [Created] (HADOOP-9937) Improvement of the group information refer frequency


Copy link to this message
-
回复: [jira] [Created] (HADOOP-9937) Improvement of the group information refer frequency
Yi Gao 2013-09-06, 01:39


发送自我的HTC S710e

----- Reply message -----
发件人: "Shinichi Yamashita (JIRA)" <[EMAIL PROTECTED]>
收件人: <[EMAIL PROTECTED]>
主题: [jira] [Created] (HADOOP-9937) Improvement of the group information refer frequency
日期: 周五, 9 月 6 日, 2013 年 6:23 上午
Shinichi Yamashita created HADOOP-9937:
------------------------------------------

             Summary: Improvement of the group information refer frequency
                 Key: HADOOP-9937
                 URL: https://issues.apache.org/jira/browse/HADOOP-9937
             Project: Hadoop Common
          Issue Type: Improvement
          Components: security
    Affects Versions: 3.0.0
            Reporter: Shinichi Yamashita
            Priority: Minor
The node (e.g. NameNode, ResourceManager) uses UGI.getGroupNames() now to get the information of the user's group who accessed it.
In UGI.getGroupsNames(), synchronized is declared, but UGI instance by various methods each time and the node get different lock in getGroupName().

For example, when cache time limit in userToGroupsMap of Groups expired and the node accepts many requests at the same time, each refers for group information in id command or JNI.
To improve the refer frequency of the group information, it should change about synchronization.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira