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

Eron Wright  commented on FLINK-2821:
-------------------------------------

Folks, would there be any issue with canonicalizing the value of 
jobmanager.rpc.address, rather than "lower-casing" it which seems hacky.    
Canonical hostnames are very important for SSL hostname verification, which 
Akka doesn't support but the post-FLIP-6 RPC could. 

Early in the discussion it was questioned whether the external address could be 
resolved from within the container - [~philipp.bussche] could you clarify?   To 
be clear, I mean 'resolve' not 'bind'.

Secondly, while this bug addressed the Akka endpoint, there are almost a 
half-dozen other endpoints within Flink.  Should we fixup all addresses that an 
external client would use?

> 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
>             Fix For: 1.2.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)

Reply via email to