[
https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398565#comment-15398565
]
Hudson commented on HADOOP-13381:
---------------------------------
SUCCESS: Integrated in Hadoop-trunk-Commit #10176 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/10176/])
HADOOP-13381. KMS clients should use KMS Delegation Tokens from current (xiao:
rev 8ebf2e95d2053cb94c6ff87ca018811fe8276f2b)
*
hadoop-common-project/hadoop-kms/src/test/java/org/apache/hadoop/crypto/key/kms/server/TestKMS.java
*
hadoop-common-project/hadoop-common/src/main/java/org/apache/hadoop/crypto/key/kms/KMSClientProvider.java
> 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.9.0, 3.0.0-alpha2
>
> 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: [email protected]
For additional commands, e-mail: [email protected]
