Philipp von dem Bussche commented on FLINK-2821:

+1 for this feature. I am orchestrating my docker environment with something 
called Rancher (http://rancher.com/). With this you might end up having 3 IP 
addresses a container can be accessed with (IP exposed to the host, docker IP 
and Rancher IP). Starting a jobmanager container via Rancher will make the RPC 
address be set to the Docker IP however if you want to use the Rancher DNS 
capabilities (which are quite cool), then you would communicate in your Rancher 
network (from taskmanager to jobmanager where taskmanager is also a container 
started under Rancher) using the Rancher IP. This however does not work at the 
moment. I worked around this for now by telling the taskmanager which Docker IP 
to connect to in order to reach the Jobmanager while starting it up but this 
however is not really nice when thinking about automation and using other 
capabilities of Rancher.
I can see this being quite a problem when using any orchestration on top of 
Docker ?!?

> 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 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

Reply via email to