[
https://issues.apache.org/jira/browse/SPARK-11765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15007740#comment-15007740
]
Jakob Odersky commented on SPARK-11765:
---------------------------------------
I think adding a "blacklist" of ports could lead to confusing debugging
experiences with no real value gained.
You can always explicitly set the web UI's port with the configuration
parameter {{spark.ui.port}}, as explained here
http://spark.apache.org/docs/latest/configuration.html
> Avoid assign UI port between browser unsafe ports (or just 4045: lockd)
> -----------------------------------------------------------------------
>
> Key: SPARK-11765
> URL: https://issues.apache.org/jira/browse/SPARK-11765
> Project: Spark
> Issue Type: Improvement
> Reporter: Jungtaek Lim
> Priority: Minor
>
> Spark UI port starts on 4040, and UI port is incremented by 1 for every
> confliction.
> In our use case, we have some drivers running at the same time, which makes
> UI port to be assigned to 4045, which is treated to unsafe port for chrome
> and mozilla.
> http://src.chromium.org/viewvc/chrome/trunk/src/net/base/net_util.cc?view=markup
> http://www-archive.mozilla.org/projects/netlib/PortBanning.html#portlist
> We would like to avoid assigning UI to these ports, or just avoid assigning
> UI port to 4045 which is too close to default port.
> If we'd like to accept this idea, I'm happy to work on it.
--
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
