[
https://issues.apache.org/jira/browse/YARN-5305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xianyin Xin updated YARN-5305:
------------------------------
Description:
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.
Supplementary: this problem happen due to that AM didn't use the service name
as the token alias in credentials, so two tokens for the same service can
co-exist in one credentials. TokenSelector can only select the first matched
token, it doesn't care if the token is valid or not.
was: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.
> 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.
> Supplementary: this problem happen due to that AM didn't use the service name
> as the token alias in credentials, so two tokens for the same service can
> co-exist in one credentials. TokenSelector can only select the first matched
> token, it doesn't care if the token is valid or not.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
