[
https://issues.apache.org/jira/browse/SPARK-18816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15743288#comment-15743288
]
Alex Bozarth commented on SPARK-18816:
--------------------------------------
Thanks for following up, I was able to recreate the issue, but I personally
wont have time to fix it before my holiday vacation. It's not a blocker still
because the log pages are still there, only the links to them are missing. You
can still access the logs for each worker via the Worker UI links found on the
Master UI.
> executor page fails to show log links if executors are added after an app is
> launched
> -------------------------------------------------------------------------------------
>
> Key: SPARK-18816
> URL: https://issues.apache.org/jira/browse/SPARK-18816
> Project: Spark
> Issue Type: Bug
> Components: Web UI
> Reporter: Yin Huai
> Attachments: screenshot-1.png
>
>
> How to reproduce with standalone mode:
> 1. Launch a spark master
> 2. Launch a spark shell. At this point, there is no executor associated with
> this application.
> 3. Launch a slave. Now, there is an executor assigned to the spark shell.
> However, there is no link to stdout/stderr on the executor page (please see
> https://issues.apache.org/jira/secure/attachment/12842649/screenshot-1.png).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
