hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Xiao Chen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-13381) KMS clients running in the same JVM should use updated KMS Delegation Token
Date Wed, 20 Jul 2016 16:38:20 GMT

     [ https://issues.apache.org/jira/browse/HADOOP-13381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Xiao Chen updated HADOOP-13381:
    Attachment: HADOOP-13381.02.patch

I extended my above thought further, and think that's the decent way to fix this.

Attaching patch 2 to demonstrate the idea, I can also verify from end-to-end if we agree on
this approach.

Could you take a look, [~asuresh]? Thanks a lot!

> 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, HADOOP-13381.02.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

To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org

View raw message