[
https://issues.apache.org/jira/browse/YARN-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17041043#comment-17041043
]
Hudson commented on YARN-10143:
-------------------------------
SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #17969 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/17969/])
YARN-10143. YARN-10101 broke Yarn logs CLI. Contributed by Adam Antal (snemeth:
rev 4af2556b48e01150851c7f273a254a16324ba843)
* (edit)
hadoop-yarn-project/hadoop-yarn/hadoop-yarn-common/src/main/java/org/apache/hadoop/yarn/logaggregation/filecontroller/ifile/LogAggregationIndexedFileController.java
> YARN-10101 broke Yarn logs CLI
> -------------------------------
>
> Key: YARN-10143
> URL: https://issues.apache.org/jira/browse/YARN-10143
> Project: Hadoop YARN
> Issue Type: Bug
> Components: yarn
> Affects Versions: 3.3.0, 3.2.2
> Reporter: Adam Antal
> Assignee: Adam Antal
> Priority: Blocker
> Attachments: YARN-10143.001.patch, YARN-10143.002.patch,
> YARN-10143.branch-3.2.001.patch
>
>
> YARN-10101 broke the Yarn logs CLI.
> In {{LogsCLI#359}} a {{ContainerLogsRequest}} has been created with null set
> as appAttemptId, while the {{LogAggregationFileController}} instances are
> configured badly to handle this case. The new JHS API works as expected for
> defined application attempt, but we should fix this.
--
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
