You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Alan Braithwaite (JIRA)" <ji...@apache.org> on 2016/01/11 19:58:39 UTC
[jira] [Commented] (SPARK-4389) Set
akka.remote.netty.tcp.bind-hostname="0.0.0.0" so driver can be located
behind NAT
[ https://issues.apache.org/jira/browse/SPARK-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15092481#comment-15092481 ]
Alan Braithwaite commented on SPARK-4389:
-----------------------------------------
So is there any hope for running spark behind a transparent proxy then? What is the preferred method for running a spark-master in an environment where things get dynamically scheduled (mesos+marathon, kubernetes, etc)?
> 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
> Affects Versions: 1.2.0
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org