[ https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15270359#comment-15270359 ]
Robert Metzger commented on FLINK-2821: --------------------------------------- I'm stopping to work on these issues for now, because Akka 2.4 requires Java 8, and I don't think its feasible yet for us to move to Java 8. If (in a few years) somebody wants to pick up my work, here is my current branch: https://github.com/rmetzger/flink/tree/flink-3662 > 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 Runtime > Reporter: Robert Metzger > Assignee: Robert Metzger > Fix For: 1.1.0 > > > 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)