[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15712187#comment-15712187
]
ASF GitHub Bot commented on FLINK-2821:
---------------------------------------
GitHub user mxm opened a pull request:
https://github.com/apache/flink/pull/2917
[FLINK-2821] use custom Akka build to listen on all interfaces
This uses Flakka (a custom Akka 2.3 build) to resolve the issue that
the bind address needs to be matching the external address of the
JobManager. With the changes applied, we can now bind to all
interfaces, e.g. via 0.0.0.0 (IPv4) or :: (Ipv6).
For this to work properly, the configuration entry
JOB_MANAGER_IPC_ADDRESS now represents the external address of the
JobManager. Consequently, it should not be resolved to an IP address
anymore because it may not be resolvable from within containered
environments. Akka treats this address as the logical address. Any
messages which are not tagged with this address will be received by
the Actor System (because we listen on all interfaces) but will be
dropped subsequently. In addition, we need the external address for
the JobManager to be able to publish its address to Zookeeper for HA
setups.
Flakka: https://github.com/mxm/flakka
Patch applied: akka/akka#15610
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/mxm/flink FLINK-2821.master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/2917.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #2917
----
commit 1ab82041f01df10b8e86da7e9b2696dd175f7e89
Author: Maximilian Michels <m...@apache.org>
Date: 2016-11-16T14:50:01Z
[FLINK-2821] use custom Akka build to listen on all interfaces
This uses Flakka (a custom Akka 2.3 build) to resolve the issue that
the bind address needs to be matching the external address of the
JobManager. With the changes applied, we can now bind to all
interfaces, e.g. via 0.0.0.0 (IPv4) or :: (Ipv6).
For this to work properly, the configuration entry
JOB_MANAGER_IPC_ADDRESS now represents the external address of the
JobManager. Consequently, it should not be resolved to an IP address
anymore because it may not be resolvable from within containered
environments. Akka treats this address as the logical address. Any
messages which are not tagged with this address will be received by
the Actor System (because we listen on all interfaces) but will be
dropped subsequently. In addition, we need the external address for
the JobManager to be able to publish it to Zookeeper for HA setups.
Flakka: https://github.com/mxm/flakka Patch applied:
https://github.com/akka/akka/pull/15610
commit 10b66ff80fec27102417e675c0e99cbad11abfc3
Author: Maximilian Michels <m...@apache.org>
Date: 2016-11-30T18:21:26Z
use staging repository for now
commit 9b8059e1b7217f56fc277a9ac886dd6150190045
Author: Maximilian Michels <m...@apache.org>
Date: 2016-12-01T14:50:11Z
adapt config and test cases
----
> Change Akka configuration to allow accessing actors from different URLs
> -----------------------------------------------------------------------
>
> Key: FLINK-2821
> URL: https://issues.apache.org/jira/browse/FLINK-2821
> Project: Flink
> Issue Type: Bug
> Components: Distributed Coordination
> Reporter: Robert Metzger
> Assignee: Maximilian Michels
>
> Akka expects the actor's URL to be exactly matching.
> As pointed out here, cases where users were complaining about this:
> http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/Error-trying-to-access-JM-through-proxy-td3018.html
> - Proxy routing (as described here, send to the proxy URL, receiver
> recognizes only original URL)
> - Using hostname / IP interchangeably does not work (we solved this by
> always putting IP addresses into URLs, never hostnames)
> - Binding to multiple interfaces (any local 0.0.0.0) does not work. Still
> no solution to that (but seems not too much of a restriction)
> I am aware that this is not possible due to Akka, so it is actually not a
> Flink bug. But I think we should track the resolution of the issue here
> anyways because its affecting our user's satisfaction.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
