You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "fengyongshe (JIRA)" <ji...@apache.org> on 2018/12/05 03:25:00 UTC
[jira] [Created] (HADOOP-15976) NameNode Performance degradation
When Single LdapServer become a bottleneck in Ldap-based mapping module
fengyongshe created HADOOP-15976:
------------------------------------
Summary: 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
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
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-dev-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-dev-help@hadoop.apache.org