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

Andrey Melentyev commented on FLINK-2821:
-----------------------------------------

[~mxm] I think getting rid of "bind" params is a good idea: I don't really see 
a use case for a separate binding port and using 0.0.0.0 to bind to all 
interfaces seems to work too. The fewer parameters the better!

As for the high availability, to be honest, I haven't though it through for 
Kubernetes yet. I tend to think that HA for Job Manager in K8S will be more 
similar to YARN case than to the standalone cluster case, i.e. it's gonna be up 
to Kubernetes to ensure there's a single Job Manager running and from the point 
of view of the Task Managers it can be abstracted by a DNS record.

> 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