[ 
https://issues.apache.org/jira/browse/KNOX-1744?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16887555#comment-16887555
 ] 

ASF subversion and git services commented on KNOX-1744:
-------------------------------------------------------

Commit 40485c5ac3edb492ffd2494d03f3a46f6eab23dd in knox's branch 
refs/heads/master from Ankur Gupta
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=40485c5 ]

KNOX-1744 - Add rewrite rules to fix executor stdout/stderr links in Spark 
History Server UI (#120)



>  [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
>             Fix For: 1.4.0
>
>         Attachments: image-2019-01-22-13-04-53-935.png, 
> image-2019-01-22-13-11-55-412.png
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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.14#76016)

Reply via email to