You are viewing a plain text version of this content. The canonical link for it is here.
Posted to yarn-issues@hadoop.apache.org by "Naganarasimha G R (JIRA)" <ji...@apache.org> on 2016/07/01 13:28:11 UTC
[jira] [Commented] (YARN-5305) Yarn Application log Aggreagation
fails due to NM can not get correct HDFS delegation token III
[ https://issues.apache.org/jira/browse/YARN-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15358963#comment-15358963 ]
Naganarasimha G R commented on YARN-5305:
-----------------------------------------
[~xinxianyin], IIUC when YARN-5175 is in place i think this issue should not occur. how about working on that instead of this ?
> 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