[
https://issues.apache.org/jira/browse/SPARK-11570?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14995693#comment-14995693
]
Sergey Soldatov commented on SPARK-11570:
-----------------------------------------
Still the question what is the reason to have a default initialization? If
initialization required, fail with some reasonable message. If it's not
required, it would be better if it works as expected. Using script is not
always suitable (process management, logging handling, etc). And as I already
mentioned, before SPARK-6440 that worked just fine, so shouldn't it be
considered as a regression?
> 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: [email protected]
For additional commands, e-mail: [email protected]
