[
https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Prabhu Joseph updated YARN-10333:
---------------------------------
Description:
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.
was:
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.
> 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 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]
