[ https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15571823#comment-15571823 ]
Stephan Ewen commented on FLINK-2821: ------------------------------------- I agree, it would be good to resolve that. It seems, though, that we are literally blocked by Akka on this. There seem to be these choices: - Abandon Java 7 (seems not a good idea at this point) - Abandon Akka (may be possible in future versions of Flink, after flip-6 and the new RPC abstraction is in) - Find a way to build a custom version of Akka 2.4 compatible with Java 7 (I know Robert tried, but it is quite hard) Any suggestions and feedback more than welcome! > 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 > > 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)