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

Hudson commented on HADOOP-13103:
---------------------------------

FAILURE: Integrated in Hadoop-trunk-Commit #9726 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/9726/])
HADOOP-13103 Group resolution from LDAP may fail on (szetszwo: rev 
f305d9c0f64fd7d085f01eaae2154ef13b05b197)
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/UserGroupInformation.java
* 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/security/LdapGroupsMapping.java
* 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/security/TestLdapGroupsMapping.java


> Group resolution from LDAP may fail on 
> javax.naming.ServiceUnavailableException
> -------------------------------------------------------------------------------
>
>                 Key: HADOOP-13103
>                 URL: https://issues.apache.org/jira/browse/HADOOP-13103
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>            Reporter: Tsz Wo Nicholas Sze
>            Assignee: Tsz Wo Nicholas Sze
>            Priority: Minor
>             Fix For: 2.7.3
>
>         Attachments: c13103_20160505.patch, c13103_20160505b.patch
>
>
> According to the 
> [javadoc|https://docs.oracle.com/javase/7/docs/api/javax/naming/ServiceUnavailableException.html],
>  ServiceUnavailableException is thrown when attempting to communicate with a 
> directory or naming service and that service is not available. It might be 
> unavailable for different reasons. For example, the server might be too busy 
> to service the request, or the server might not be registered to service any 
> requests, etc.
> We should retry on it.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to