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

Xiao Chen updated HADOOP-13381:
-------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: 3.0.0-alpha2
                   2.9.0
           Status: Resolved  (was: Patch Available)

Committed to trunk and branch-2. There is a minor conflict (imports) when 
backporting to branch-2, compiled and made sure {{TestKMS}} pass before pushing.

Thanks a lot [~asuresh] for the thoughtful reviews, and [~andrew.wang] for 
chiming in!

> 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]

Reply via email to