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 "Adam Antal (Jira)" <ji...@apache.org> on 2020/02/18 09:29:00 UTC

[jira] [Updated] (YARN-10143) YARN-10101 broke Yarn logs CLI

     [ https://issues.apache.org/jira/browse/YARN-10143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Adam Antal updated YARN-10143:
------------------------------
    Attachment: YARN-10143.001.patch

> 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-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-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org