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 2016/10/21 22:01:01 UTC
[jira] [Updated] (HADOOP-13381) KMS clients should use KMS
Delegation Tokens from current UGI.
[ https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Xiao Chen updated HADOOP-13381:
-------------------------------
Fix Version/s: (was: 2.9.0)
2.8.0
> KMS clients should use KMS Delegation Tokens from current UGI.
> --------------------------------------------------------------
>
> Key: HADOOP-13381
> URL: https://issues.apache.org/jira/browse/HADOOP-13381
> Project: Hadoop Common
> Issue Type: Bug
> Components: kms
> Affects Versions: 2.6.0
> Reporter: Xiao Chen
> Assignee: Xiao Chen
> Priority: Critical
> Fix For: 2.8.0, 3.0.0-alpha1
>
> Attachments: HADOOP-13381.01.patch, HADOOP-13381.02.patch, HADOOP-13381.03.patch, HADOOP-13381.04.patch
>
>
> When {{/tmp}} is setup as an EZ, one may experience YARN log aggregation failure after the very first KMS token is expired. The MR job itself runs fine though.
> When this happens, YARN NodeManager's log will show {{AuthenticationException}} with {{token is expired}} / {{token can't be found in cache}}, depending on whether the expired token is removed by the background or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org