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 "Prabhu Joseph (Jira)" <ji...@apache.org> on 2020/06/30 19:04:00 UTC
[jira] [Updated] (YARN-10333) YarnClient obtain Delegation Token
for Log Aggregation Path
[ https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Prabhu Joseph updated YARN-10333:
---------------------------------
Attachment: YARN-10333-001.patch
> YarnClient obtain Delegation Token for Log Aggregation Path
> -----------------------------------------------------------
>
> Key: YARN-10333
> URL: https://issues.apache.org/jira/browse/YARN-10333
> Project: Hadoop YARN
> Issue Type: Improvement
> Components: log-aggregation
> Affects Versions: 3.3.0
> Reporter: Prabhu Joseph
> Assignee: Prabhu Joseph
> Priority: Major
> Attachments: YARN-10333-001.patch
>
>
> There are use cases where Yarn Log Aggregation Path is configured to a FileSystem like S3 or ABFS different from what is configured in fs.defaultFS (HDFS). Log Aggregation fails as the client has token only for fs.defaultFS and not for log aggregation path.
> This Jira is to improve YarnClient by obtaining delegation token for log aggregation path and add it to the Credential of Container Launch Context similar to Timeline Delegation Token.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org