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 "Chao Sun (Jira)" <ji...@apache.org> on 2022/01/04 22:45:00 UTC

[jira] [Updated] (YARN-11020) [UI2] No container is found for an application attempt with a single AM container

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

Chao Sun updated YARN-11020:
----------------------------
    Fix Version/s: 3.3.2
                       (was: 3.3.3)

> [UI2] No container is found for an application attempt with a single AM container
> ---------------------------------------------------------------------------------
>
>                 Key: YARN-11020
>                 URL: https://issues.apache.org/jira/browse/YARN-11020
>             Project: Hadoop YARN
>          Issue Type: Bug
>          Components: yarn-ui-v2
>            Reporter: Andras Gyori
>            Assignee: Andras Gyori
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.2
>
>         Attachments: YARN-11020-branch-3.3.001.patch
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> In UI2 for an application under the Logs tab, No container data available message is shown if the application attempt only submitted a single container (which is the AM container). 
> The culprit of the issue is that the response from YARN is not consistent, because for a single container it looks like:
> {noformat}
> {
>     "containerLogsInfo": {
>         "containerLogInfo": [
>             {
>                 "fileName": "prelaunch.out",
>                 "fileSize": "100",
>                 "lastModifiedTime": "Mon Nov 29 09:28:16 +0000 2021"
>             },
>             {
>                 "fileName": "directory.info",
>                 "fileSize": "2296",
>                 "lastModifiedTime": "Mon Nov 29 09:28:16 +0000 2021"
>             },
>             {
>                 "fileName": "stderr",
>                 "fileSize": "1722",
>                 "lastModifiedTime": "Mon Nov 29 09:28:28 +0000 2021"
>             },
>             {
>                 "fileName": "prelaunch.err",
>                 "fileSize": "0",
>                 "lastModifiedTime": "Mon Nov 29 09:28:16 +0000 2021"
>             },
>             {
>                 "fileName": "stdout",
>                 "fileSize": "0",
>                 "lastModifiedTime": "Mon Nov 29 09:28:16 +0000 2021"
>             },
>             {
>                 "fileName": "syslog",
>                 "fileSize": "38551",
>                 "lastModifiedTime": "Mon Nov 29 09:28:28 +0000 2021"
>             },
>             {
>                 "fileName": "launch_container.sh",
>                 "fileSize": "5013",
>                 "lastModifiedTime": "Mon Nov 29 09:28:16 +0000 2021"
>             }
>         ],
>         "logAggregationType": "AGGREGATED",
>         "containerId": "container_1638174027957_0008_01_000001",
>         "nodeId": "da175178c179:43977"
>     }
> }{noformat}
> As for applications with multiple containers it looks like:
> {noformat}
> {
>     "containerLogsInfo": [{
>         ....
>     }, { .... }]
> }{noformat}
> We can not change the response of the endpoint due to backward compatibility, therefore we need to make UI2 be able to handle both scenarios.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: yarn-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: yarn-issues-help@hadoop.apache.org