hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "sanjay kenganahalli vamanna (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-9956) LDAP PERFORMANCE ISSUE AND FAIL OVER
Date Wed, 16 Mar 2016 13:08:33 GMT

    [ https://issues.apache.org/jira/browse/HDFS-9956?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15197274#comment-15197274

sanjay kenganahalli vamanna commented on HDFS-9956:

Thanks for replying,The issue in this jira about timeout that causes the nematode failure.
I know you are taking about faster LDAP response using caching daemon, That may speed up the
ldap response but is not related to timeout(10 sec).


> ------------------------------------
>                 Key: HDFS-9956
>                 URL: https://issues.apache.org/jira/browse/HDFS-9956
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: sanjay kenganahalli vamanna
> The typical LDAP group name resolution works well under typical scenarios. However, we
have seen cases where a user is mapped to many groups (in an extreme case, a user is mapped
to more than 100 groups). The way it's being implemented now makes this case super slow resolving
groups from ActiveDirectory and making the namenode to failover.
> Instead of failover, we can use the parameter(ha.zookeeper.session-timeout.ms) in the
getgroups method to time-out and send the failed response back to the user so that we can
prevent name node failover. 

This message was sent by Atlassian JIRA

View raw message