[
https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380359#comment-15380359
]
Arun Suresh commented on HADOOP-13381:
--------------------------------------
Thanks for the opening this [~xiaochen]..
I think your approach is definitely simpler than modifying the cache to key
with a composite key of URI + ugi current user.
But I think the bigger issue is that it looks like the {{ClientContext}} in
which the {{KeyProviderCache}} is maintained is not a per user cache. Can you
confirm [~cmccabe] / [~andrew.wang]?
> KMS clients running in the same JVM should use updated KMS Delegation Token
> ---------------------------------------------------------------------------
>
> 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
> Attachments: HADOOP-13381.01.patch
>
>
> When {{/tmp}} is setup as an EZ, one may experience YARN log aggregation
> failure after the KMS token is expired. The MR job itself runs find though.
> When this happens, YARN NodeManager's log will show
> {{AuthenticationException}} with token is expire / 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]
