[
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15675221#comment-15675221
]
Maximilian Michels commented on FLINK-2821:
-------------------------------------------
Thanks you for your answers, [~philipp.bussche] and [~melentye]. Very helpful!
I'm thinking about getting rid of the bind settings again and simply defaulting
to "0.0.0.0" for the bind address. It seems that this is the only useful
setting in an environment where we can't resolve the correct bind ip from
within the JobManager container. The bind port setting might still be useful
though.
The only thing that might be missing is support for highly availability setups.
Currently, we rely on the JobManager to publish its address to Zookeeper. If it
uses ({{jobmanager.rpc.address}}) there and never tries to resolve this
address, we should be fine. I have to double check the code if that is actually
the case.
> 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)
