[ 
https://issues.apache.org/jira/browse/FLINK-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15714889#comment-15714889
 ] 

ASF GitHub Bot commented on FLINK-2821:
---------------------------------------

Github user StephanEwen commented on the issue:

    https://github.com/apache/flink/pull/2917
  
    I have to dig back a bit (long time since I worked on that), but I thought 
the IPv6 addresses issue was quite tricky one and the normalization code for 
address representations was necessary.
    
    Can we try and preserve both in some way? When a logical hostname is 
specified, we use that one in the Akka URLs. When an IP address is specified, 
we normalize it and use it.
    
    That way we only "loose" the ability to use mixed hostname/IP-address 
configurations, but that would be okay, I guess.


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

Reply via email to