You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Nicolas Colomer (JIRA)" <ji...@apache.org> on 2019/01/22 12:13:00 UTC

[jira] [Updated] (KNOX-1744) [Spark History UI Service] Executor logs (stdout/stderr) links are broken

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

Nicolas Colomer updated KNOX-1744:
----------------------------------
    Summary:  [Spark History UI Service] Executor logs (stdout/stderr) links are broken  (was:  [SparkHistory UI Service] Executor logs (stdout/stderr) links are broken)

>  [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> --------------------------------------------------------------------------
>
>                 Key: KNOX-1744
>                 URL: https://issues.apache.org/jira/browse/KNOX-1744
>             Project: Apache Knox
>          Issue Type: Bug
>    Affects Versions: 1.2.0
>            Reporter: Nicolas Colomer
>            Priority: Minor
>         Attachments: image-2019-01-22-13-04-53-935.png, image-2019-01-22-13-11-55-412.png
>
>
> The executor logs (stdout/stderr) links from the Yarn UI Service all directly points to the slaves nodes.
> !image-2019-01-22-13-11-55-412.png!
> Eg. the link:
> {noformat}
> http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_000001/hadoop/stdout?start=-4096{noformat}
> Should have been instead: 
> {noformat}
> https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_000001/hadoop?scheme=http&host=emr-slave-hostname&port=8042{noformat}
> And finally respect pattern:
> {noformat}
> https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container id}/hadoop?scheme=http&host={executor host}&port=8042 {noformat}
> I guess adding some voodoo in the Knox yarnui's [rewrite.xml|https://github.com/apache/knox/blob/master/gateway-service-definitions/src/main/resources/services/yarnui/2.7.0/rewrite.xml] file might be enough to fix this.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)