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

XML

Word

Printable

JSON

Details

Type: Bug
Status: Resolved
Priority: Minor
Resolution: Fixed
Affects Version/s: 1.2.0, 1.3.0
Fix Version/s: 1.4.0
Component/s: None
Labels:
None

Description

The executor logs (stdout/stderr) links from the Yarn UI Service all directly points to the slaves nodes.

Eg. the link:

http://emr-slave-hostname:8042/node/containerlogs/container_1547901130703_0034_01_000001/hadoop/stdout?start=-4096

Should have been instead:

https://knox/gateway/cluster/yarn/nodemanager/node/containerlogs/container_1547901130703_0034_01_000001/hadoop?scheme=http&host=emr-slave-hostname&port=8042

And finally respect pattern:

https://knox/gateway/emr/yarn/nodemanager/node/containerlogs/{your container id}/hadoop?scheme=http&host={executor host}&port=8042

I guess adding some voodoo in the Knox yarnui's rewrite.xml file might be enough to fix this.

Attachments

- Sort By Name
- Sort By Date
- Ascending
- Descending

image-2019-01-22-13-11-55-412.png
22/Jan/19 12:11
92 kB
Nicolas Colomer
image-2019-01-22-13-04-53-935.png
22/Jan/19 12:04
322 kB
Nicolas Colomer

Issue Links

relates to

KNOX-2647 [Spark History UI Service] Executor logs (stdout/stderr) links are broken with JobHostory Service

Resolved

links to

GitHub Pull Request #120

Activity

People

Assignee:: Ankur Gupta

Reporter:: Nicolas Colomer

Votes:: 1 Vote for this issue

Watchers:: 6 Start watching this issue

Dates

Created:: 22/Jan/19 12:04

Updated:: 25/Aug/21 17:17

Resolved:: 18/Jul/19 02:36

Time Tracking

Estimated:

Not Specified

Remaining:

Logged:

0.5h