[
https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17149595#comment-17149595
]
Prabhu Joseph edited comment on YARN-10333 at 7/1/20, 5:41 PM:
---------------------------------------------------------------
[[email protected]] Can you review this Jira when you get time. Thanks.
Have verified with below combinations:
*fs.defaultFS Log Aggregation Path*
hdfs://nm1 s3a://tmp/app-logs
hdfs://nm1 abfs://tmp/app-logs
hdfs://nm1 hdfs://nm2/tmp/app-logs
hdfs://nm1 hdfs://nm1/tmp/app-logs
was (Author: prabhu joseph):
[[email protected]] Can you review this Jira when you get time. Thanks.
Have verified with below combinations:
*fs.defaultFS Log Aggregation Path*
hdfs://nm1 s3a://tmp/app-logs
hdfs://nm1 abfs://tmp/app-logs
hdfs://nm1 hdfs://nm2/tmp/app-logs
hdfs://nm1 hdfs://nm1/tmp/app-logs
> 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, YARN-10333-002.patch,
> YARN-10333-003.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 how it does for Timeline Delegation Token.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
