[
https://issues.apache.org/jira/browse/SPARK-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jim Lohse updated SPARK-11570:
------------------------------
Comment: was deleted
(was: [~srowen] Do you mean SPARK_LOCAL_IP? I don't see SPARK_LOCAL_HOSTNAME in
spark-env.sh. Thanks, if it exists and needs to be added to spark-env.sh I will
submit a pull request.)
> ambiguous hostname resolving during startup
> -------------------------------------------
>
> Key: SPARK-11570
> URL: https://issues.apache.org/jira/browse/SPARK-11570
> Project: Spark
> Issue Type: Bug
> Components: Spark Core
> Affects Versions: 1.4.0, 1.4.1, 1.5.0, 1.5.1
> Environment: standalone
> Reporter: Sergey Soldatov
>
> when master is running in standalone mode, it expects that the hostname will
> be provided by --host. This is done by the start-master.sh script which sets
> --ip to `hostname` (doesn't it looks weird?).
> If someone running master directly (without start-master.sh), the hostname
> will be initialized as var host = Utils.localHostName(). Before SPARK-6440
> that was exactly the host name where master was started. But now it returns
> ip address instead. That would lead to worker connectivity problems (like you
> may observer in BIGTOP-2113). If ip addresses are prohibited, than var host
> should not be initialized in that way.
> Possible solutions - return the logic to set it to the host name or fail if
> no --host argument was provided.
--
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
