You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Xiao Chen (JIRA)" <ji...@apache.org> on 2018/04/03 18:17:00 UTC
[jira] [Updated] (HADOOP-14987) Improve KMSClientProvider log
around delegation token checking
[ https://issues.apache.org/jira/browse/HADOOP-14987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-14987:
-------------------------------
Fix Version/s: 2.9.2
2.8.4
2.10.0
> Improve KMSClientProvider log around delegation token checking
> --------------------------------------------------------------
>
> Key: HADOOP-14987
> URL: https://issues.apache.org/jira/browse/HADOOP-14987
> Project: Hadoop Common
> Issue Type: Improvement
> Affects Versions: 2.7.3
> Reporter: Xiaoyu Yao
> Assignee: Xiaoyu Yao
> Priority: Major
> Fix For: 3.0.0, 2.10.0, 2.8.4, 2.9.2
>
> Attachments: HADOOP-14987.001.patch, HADOOP-14987.002.patch, HADOOP-14987.003.patch, HADOOP-14987.004.patch, HADOOP-14987.005.patch
>
>
> KMSClientProvider#containsKmsDt uses SecurityUtil.buildTokenService(addr) to build the key to look for KMS-DT from the UGI's token map. The token lookup key here varies depending on the KMSClientProvider's configuration value for hadoop.security.token.service.use_ip. In certain cases, the token obtained with non-matching hadoop.security.token.service.use_ip setting will not be recognized by KMSClientProvider. This ticket is opened to improve logs for troubleshooting KMS delegation token related issues like this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org