[
https://issues.apache.org/jira/browse/HADOOP-9322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13583353#comment-13583353
]
Harsh J commented on HADOOP-9322:
---------------------------------
However, http://osdir.com/ml/java.sun.jndi/2005-09/msg00005.html does note that
some systems may disobey this. FWIW, lets make it work for systems that do
respect it at least.
> LdapGroupsMapping doesn't seem to set a timeout for its directory search
> ------------------------------------------------------------------------
>
> Key: HADOOP-9322
> URL: https://issues.apache.org/jira/browse/HADOOP-9322
> Project: Hadoop Common
> Issue Type: Improvement
> Components: security
> Affects Versions: 2.0.3-alpha
> Reporter: Harsh J
> Priority: Minor
> Labels: performance
>
> We don't appear to be setting a timeout via
> http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/SearchControls.html#setTimeLimit(int)
> before we search with
> http://docs.oracle.com/javase/6/docs/api/javax/naming/directory/DirContext.html#search(javax.naming.Name,%20java.lang.String,%20javax.naming.directory.SearchControls).
> This may occasionally lead to some unwanted NN pauses due to lock-holding on
> the operations that do group lookups. A timeout is better to define than rely
> on "0" (infinite wait).
--
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
