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

Shuai Lin updated SPARK-18171:
------------------------------
    Description: In [[SPARK-4563]] we added the support for the driver to 
advertise a different hostname/ip ({{spark.driver.host}} to the executors other 
than the hostname/ip the driver actually binds to 
({{spark.driver.bindAddress}}). But in the mesos webui's frameworks page, it 
still shows the driver's binds hostname/ip (though the web ui link is correct). 
We should fix it to make them consistent.  (was: In INF-4563 we added the 
support for the driver to advertise a different hostname/ip 
({{spark.driver.host}} to the executors other than the hostname/ip the driver 
actually binds to ({{spark.driver.bindAddress}}). But in the mesos webui's 
frameworks page, it still shows the driver's binds hostname/ip (though the web 
ui link is correct). We should fix it to make them consistent.)

> Show correct framework address in mesos master web ui when the advertised 
> address is used
> -----------------------------------------------------------------------------------------
>
>                 Key: SPARK-18171
>                 URL: https://issues.apache.org/jira/browse/SPARK-18171
>             Project: Spark
>          Issue Type: Improvement
>          Components: Mesos
>            Reporter: Shuai Lin
>            Priority: Minor
>
> In [[SPARK-4563]] we added the support for the driver to advertise a 
> different hostname/ip ({{spark.driver.host}} to the executors other than the 
> hostname/ip the driver actually binds to ({{spark.driver.bindAddress}}). But 
> in the mesos webui's frameworks page, it still shows the driver's binds 
> hostname/ip (though the web ui link is correct). We should fix it to make 
> them consistent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to