[
https://issues.apache.org/jira/browse/YARN-10333?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17154290#comment-17154290
]
Hudson commented on YARN-10333:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #18422 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/18422/])
YARN-10333. YarnClient obtain Delegation Token for Log Aggregation Path.
(sunilg: rev 5dd270e2085c8e8c3428287ed6f0c541a5548a31)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/test/java/org/apache/hadoop/yarn/client/api/impl/TestYarnClientImpl.java
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/src/main/java/org/apache/hadoop/yarn/client/api/impl/YarnClientImpl.java
* (edit) hadoop-yarn-project/hadoop-yarn/hadoop-yarn-client/pom.xml
> 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
> Fix For: 3.4.0
>
> 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: yarn-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org
