hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Wang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HADOOP-13381) KMS clients running in the same JVM should use updated KMS Delegation Token
Date Fri, 15 Jul 2016 23:24:20 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15380297#comment-15380297
] 

Andrew Wang commented on HADOOP-13381:
--------------------------------------

[~asuresh] do you think you can review this one? The fix is a one-liner, but the discussion
here is mostly about YARN, and it looks like you wrote the original cache code.

> 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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org


Mime
View raw message