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

Josh Rosen updated SPARK-4389:
------------------------------
    Description: 
We should set {{akka.remote.netty.tcp.bind-hostname="0.0.0.0"}} in our Akka 
configuration so that Spark drivers can be located behind NATs / work with 
weird DNS setups.

This is blocked by upgrading our Akka version, since this configuration is not 
present Akka 2.3.4.  There might be a different approach / workaround that 
works on our current Akka version, though.

EDIT: this is blocked by Akka 2.4, since this feature is only available in the 
2.4 snapshot release.

  was:
We should set {{akka.remote.netty.tcp.bind-hostname="0.0.0.0"}} in our Akka 
configuration so that Spark drivers can be located behind NATs / work with 
weird DNS setups.

This is blocked by upgrading our Akka version, since this configuration is not 
present Akka 2.3.4.  There might be a different approach / workaround that 
works on our current Akka version, though.


> Set akka.remote.netty.tcp.bind-hostname="0.0.0.0" so driver can be located 
> behind NAT
> -------------------------------------------------------------------------------------
>
>                 Key: SPARK-4389
>                 URL: https://issues.apache.org/jira/browse/SPARK-4389
>             Project: Spark
>          Issue Type: Improvement
>          Components: Spark Core
>            Reporter: Josh Rosen
>            Priority: Minor
>
> We should set {{akka.remote.netty.tcp.bind-hostname="0.0.0.0"}} in our Akka 
> configuration so that Spark drivers can be located behind NATs / work with 
> weird DNS setups.
> This is blocked by upgrading our Akka version, since this configuration is 
> not present Akka 2.3.4.  There might be a different approach / workaround 
> that works on our current Akka version, though.
> EDIT: this is blocked by Akka 2.4, since this feature is only available in 
> the 2.4 snapshot release.



--
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