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

Marcelo Vanzin updated SPARK-22836:
-----------------------------------
    Description: 
-I think this was mainly caused by SPARK-15951; that changed modified the 
executors page to read data from the REST API, and in 2.1 and 2.2 the REST API 
does not return the driver as an executor. So no information about the driver 
is shown in that page at all.- (Edit: bug is unrelated to the aforementioned 
bug.)

In 2.3 the driver executor is listed, but it is doesn't have any log links.

  was:
I think this was mainly caused by SPARK-15951; that changed modified the 
executors page to read data from the REST API, and in 2.1 and 2.2 the REST API 
does not return the driver as an executor. So no information about the driver 
is shown in that page at all.

In 2.3 the driver is listed, but it is doesn't have any log links.

It shouldn't be hard to fix both cases, but completely separate fixes will be 
needed for 2.3 and for the previous branches.


> Executors page is not showing driver logs links
> -----------------------------------------------
>
>                 Key: SPARK-22836
>                 URL: https://issues.apache.org/jira/browse/SPARK-22836
>             Project: Spark
>          Issue Type: Bug
>          Components: Web UI
>    Affects Versions: 2.3.0
>            Reporter: Marcelo Vanzin
>
> -I think this was mainly caused by SPARK-15951; that changed modified the 
> executors page to read data from the REST API, and in 2.1 and 2.2 the REST 
> API does not return the driver as an executor. So no information about the 
> driver is shown in that page at all.- (Edit: bug is unrelated to the 
> aforementioned bug.)
> In 2.3 the driver executor is listed, but it is doesn't have any log links.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to