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

Gurvinder commented on SPARK-15487:
-----------------------------------

The setting needs to be set for all the application, master and worker 
components as mentioned in document.

"spark.ui.reverseProxy: Enable running Spark Master as reverse proxy for worker 
and application UIs. In this mode, Spark master will reverse proxy the worker 
and application UIs to enable access without requiring direct access to their 
hosts. Use it with caution, as worker and application UI will not be accessible 
directly, you will only be able to access them through spark master/proxy 
public URL. This setting affects all the workers and application UIs running in 
the cluster and must be set on all the workers, drivers and masters."

I set this in spark-default.conf on all the components and it works. The other 
parameter spark.ui.reverseProxyUrl is required if you running master itself 
behind the proxy, then this value must be equal to the FQDN of proxy. Hope that 
helps.

> Spark Master UI to reverse proxy Application and Workers UI
> -----------------------------------------------------------
>
>                 Key: SPARK-15487
>                 URL: https://issues.apache.org/jira/browse/SPARK-15487
>             Project: Spark
>          Issue Type: Improvement
>          Components: Web UI
>    Affects Versions: 1.6.0, 1.6.1
>            Reporter: Gurvinder
>            Assignee: Gurvinder
>            Priority: Minor
>             Fix For: 2.1.0
>
>
> Currently when running in Standalone mode, Spark UI's link to workers and 
> application drivers are pointing to internal/protected network endpoints. So 
> to access workers/application UI user's machine has to connect to VPN or need 
> to have access to internal network directly.
> Therefore the proposal is to make Spark master UI reverse proxy this 
> information back to the user. So only Spark master UI needs to be opened up 
> to internet. 
> The minimal changes can be done by adding another route e.g. 
> http://spark-master.com/target/<endpoint>/ so when request goes to target, 
> ProxyServlet kicks in and takes the <endpoint> and forwards the request to it 
> and send response back to user.
> More information about discussions for this features can be found on this 
> mailing list thread 
> http://apache-spark-developers-list.1001551.n3.nabble.com/spark-on-kubernetes-tc17599.html



--
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

Reply via email to