[ https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15575226#comment-15575226 ]
Maximilian Michels commented on FLINK-2821: ------------------------------------------- [~philipp.bussche] Which version of Flink do you want to use? I've assembled a Flink 1.1.3 with a custom Akka version: http://people.apache.org/~mxm/flink-1.1.3-custom.zip In flink-conf.yaml, you'll find two new address configuration entries which allow you to specify a bind address: {noformat} jobmanager.rpc.address: externalHostName jobmanager.rpc.port: 6123 jobmanager.rpc.bind-address: localhost jobmanager.rpc.bind-port: 6123 {noformat} Would be great if you could give it a try! > 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)