[
https://issues.apache.org/jira/browse/KNOX-2647?focusedWorklogId=641885&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-641885
]
ASF GitHub Bot logged work on KNOX-2647:
----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Aug/21 18:19
Start Date: 25/Aug/21 18:19
Worklog Time Spent: 10m
Work Description: moresandeep merged pull request #485:
URL: https://github.com/apache/knox/pull/485
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 641885)
Time Spent: 20m (was: 10m)
> [Spark History UI Service] Executor logs (stdout/stderr) links are broken
> with JobHostory Service
> --------------------------------------------------------------------------------------------------
>
> Key: KNOX-2647
> URL: https://issues.apache.org/jira/browse/KNOX-2647
> Project: Apache Knox
> Issue Type: Bug
> Affects Versions: 1.5.0
> Reporter: Xiao Yu
> Priority: Minor
> Attachments: KNOX-2647.patch, spark-history-ui.png
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Currently with Knox 1.5.0 on a cluster with both Spark History Server and MR
> JobHistory Server running the stdout and stderr links target the MR
> JobHistory Server Web UI directly. For us this breaks them because we require
> Knox fronted proxy access to the MR JobHistory Server on our production
> cluster.
> !spark-history-ui.png|width=899,height=493!
> A similar issue was raised in:
> - KNOX-1744
> - KNOX-1988
> However in this case the links are going to the MR JobHistory Server not YARN
> RM so the targets are different and the previous rewrites do not apply.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
