[ https://issues.apache.org/jira/browse/SPARK-4389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14259020#comment-14259020
]
Shixiong Zhu commented on SPARK-4389:
-------------------------------------
Try to make sure I understand this issue:
The driver binds to `example.com` and it has two IPs: `10.11.0.3`, `192.168.0.3`. In the driver
side, `example.com` is resolved to `192.168.0.3`, so Akka will bind to `192.168.0.3`. But
in the executor side, `example.com` is resolved to `10.11.0.3`. Then the packets sent from
the executor side to the driver will be dropped.
Is it right?
> 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: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org
|