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

Hudson commented on HADOOP-16199:
---------------------------------

FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16302 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16302/])
HADOOP-16199. KMSLoadBlanceClientProvider does not select token (github: rev 
f41f938b2e498161da96bfad77410871a3a85728)
* (edit) 
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/LoadBalancingKMSClientProvider.java
* (edit) 
hadoop-common-project/hadoop-common/src/test/java/org/apache/hadoop/crypto/key/kms/TestLoadBalancingKMSClientProvider.java


> KMSLoadBlanceClientProvider does not select token correctly
> -----------------------------------------------------------
>
>                 Key: HADOOP-16199
>                 URL: https://issues.apache.org/jira/browse/HADOOP-16199
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 3.0.2
>            Reporter: Xiaoyu Yao
>            Assignee: Xiaoyu Yao
>            Priority: Major
>              Labels: kms
>             Fix For: 3.3.0
>
>
> After HADOOP-14445 and HADOOP-15997, there are still cases where 
> KMSLoadBlanceClientProvider does not select token correctly. 
> Here is the use case:
> The new configuration key 
> hadoop.security.kms.client.token.use.uri.format=true is set cross all the 
> cluster, including both Submitter and Yarn RM(renewer), which is not covered 
> in the test matrix in this [HADOOP-14445 
> comment|https://issues.apache.org/jira/browse/HADOOP-14445?focusedCommentId=16505761&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16505761].
> I will post the debug log and the proposed fix shortly, cc: [~xiaochen] and 
> [~jojochuang].



--
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