spark-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sean Owen (JIRA)" <>
Subject [jira] [Commented] (SPARK-11570) ambiguous hostname resolving during startup
Date Mon, 09 Nov 2015 06:50:10 GMT


Sean Owen commented on SPARK-11570:

Hm, OK then sounds like SPARK-10149. The answer is to set {{SPARK_LOCAL_HOSTNAME}}. I am not
100% clear on this but I think that was always the intent, to explicitly control what the
service binds to.

> ambiguous hostname resolving during startup
> -------------------------------------------
>                 Key: SPARK-11570
>                 URL:
>             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 script which sets --ip to `hostname` (doesn't
it looks weird?). 
> If someone running master directly (without, 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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message