[
https://issues.apache.org/jira/browse/HADOOP-15976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
fengyongshe updated HADOOP-15976:
---------------------------------
Description:
2000+ nodes cluster, We use OpenLdap to manager users and groups . when
LdapGroupsMapping used , Group look-up cause segment fault include NameNode
Performance degradation & name node crashes .
WARN security.Groups: Potential performance problem:
getGroups(user=xxxx) took 46817 milliseconds.
INFO namenode.FSNamesysatem(FSNamesystemLoclk.java:writeUnlock(252))-
FSNameSystem write lock held for 46817 ms via java.lang.thread.getStackTrace
We Found the Ldap Server become the bottleneck for NN operations， Single Ldap
Server only support hundred request per seconds
ps. The Server was running nslcd
was:
2000+ nodes cluster, We use OpenLdap to manager users and groups . when
LdapGroupsMapping used , Group look-up cause segment fault include NameNode
Performance degradation & name node crashes .
WARN security.Groups: Potential performance problem:
getGroups(user=xxxx) took 46817 milliseconds.
INFO namenode.FSNamesysatem(FSNamesystemLoclk.java:writeUnlock(252))-
FSNameSystem write lock held for 46817 ms via java.lang.thread.getStackTrace
ps. The Server was running nslcd
> NameNode Performance degradation When Single LdapServer become a bottleneck
> in Ldap-based mapping module
> ----------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-15976
> URL: https://issues.apache.org/jira/browse/HADOOP-15976
> Project: Hadoop Common
> Issue Type: Improvement
> Components: common
> Reporter: fengyongshe
> Priority: Major
> Attachments: image003(12-05-1(12-05-10-36-26).jpg
>
>
> 2000+ nodes cluster, We use OpenLdap to manager users and groups . when
> LdapGroupsMapping used , Group look-up cause segment fault include NameNode
> Performance degradation & name node crashes .
> WARN security.Groups: Potential performance problem:
> getGroups(user=xxxx) took 46817 milliseconds.
> INFO namenode.FSNamesysatem(FSNamesystemLoclk.java:writeUnlock(252))-
> FSNameSystem write lock held for 46817 ms via java.lang.thread.getStackTrace
> We Found the Ldap Server become the bottleneck for NN operations， Single Ldap
> Server only support hundred request per seconds
> ps. The Server was running nslcd
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
