[
https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiao Chen updated HADOOP-13381:
-------------------------------
Description:
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.
was:
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 expire}} / {{token can't be found in cache}}, depending on
whether the expired token is removed by the background or not.
> 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 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-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-issues-h...@hadoop.apache.org
