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 "Abhinaba Sarkar (Jira)" <ji...@apache.org> on 2021/06/07 10:02:00 UTC

[jira] [Updated] (YARN-10792) Set Completed AppAttempt LogsLink to Log Server Url

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

Abhinaba Sarkar updated YARN-10792:
-----------------------------------
    Attachment: YARN-10792-002.patch

> Set Completed AppAttempt LogsLink to Log Server Url
> ---------------------------------------------------
>
>                 Key: YARN-10792
>                 URL: https://issues.apache.org/jira/browse/YARN-10792
>             Project: Hadoop YARN
>          Issue Type: Improvement
>          Components: webapp
>    Affects Versions: 3.3.0
>            Reporter: Prabhu Joseph
>            Assignee: Abhinaba Sarkar
>            Priority: Major
>         Attachments: YARN-10792-001.patch, YARN-10792-002.patch
>
>
> Completed AppAttempts listed by YARN UI has logslink pointing to the NodeManager containerlogs url. The completed container logs will be under aggregated log path and so NM ContainerLogsPage redirects to Log Server Url. On frequent Scale Down, these NMs won't be available and so makes difficulty to look for appattempt logs of completed apps from RM UI. Setting the logslink for Completed AppAttempts to LogServer url will avoid this issue. 



--
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