hadoop-yarn-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Naganarasimha G R (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (YARN-5305) Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation token III
Date Tue, 05 Jul 2016 05:13:11 GMT

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

Naganarasimha G R commented on YARN-5305:
-----------------------------------------

Sure [~xinxianyin], i have linked both these jira's and if we are not dependent on the tokens
given by user and as per the Vinod's comment * we simply always manage our own tokens for
localization and log-aggregation for long-running applications / services* i think would be
perfect solution 

> Yarn Application log Aggreagation fails due to NM can not get correct HDFS delegation
token III
> -----------------------------------------------------------------------------------------------
>
>                 Key: YARN-5305
>                 URL: https://issues.apache.org/jira/browse/YARN-5305
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn
>            Reporter: Xianyin Xin
>
> Different with YARN-5098 and YARN-5302, this problem happens when AM submits a startContainer
request with a new HDFS token (say, tokenB) which is not managed by YARN, so two tokens exist
in the credentials of the user on NM, one is tokenB, the other is the one renewed on RM (tokenA).
If tokenB is selected when connect to HDFS and tokenB expires, exception happens.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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


Mime
View raw message