Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
Reviewed
Description
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:
{ "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" } }
As for applications with multiple containers it looks like:
{ "containerLogsInfo": [{ .... }, { .... }] }
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.
Attachments
Attachments
Issue Links
- links to