[ 
https://issues.apache.org/jira/browse/HADOOP-15976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16866297#comment-16866297
 ] 

Hadoop QA commented on HADOOP-15976:
------------------------------------

| (x) *{color:red}-1 overall{color}* |
\\
\\
|| Vote || Subsystem || Runtime || Comment ||
| {color:blue}0{color} | {color:blue} reexec {color} | {color:blue}  0m  
0s{color} | {color:blue} Docker mode activated. {color} |
| {color:red}-1{color} | {color:red} patch {color} | {color:red}  0m  7s{color} 
| {color:red} HADOOP-15976 does not apply to trunk. Rebase required? Wrong 
Branch? See https://wiki.apache.org/hadoop/HowToContribute for help. {color} |
\\
\\
|| Subsystem || Report/Notes ||
| JIRA Issue | HADOOP-15976 |
| JIRA Patch URL | 
https://issues.apache.org/jira/secure/attachment/12950661/HADOOP-15976.patch |
| Console output | 
https://builds.apache.org/job/PreCommit-HADOOP-Build/16326/console |
| Powered by | Apache Yetus 0.8.0   http://yetus.apache.org |


This message was automatically generated.



> 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
>    Affects Versions: 3.1.1
>            Reporter: fengyongshe
>            Assignee: fengyongshe
>            Priority: Major
>         Attachments: HADOOP-15976.patch, 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]

Reply via email to